theater.needle.tools WebMCP Tools, Schemas & Agent Capabilities

theater.needle.tools

live Unverified (seed import) Media & Personal 31 tools imperative implementation

A paper theatre driven by the AI agent in your browser: it decides the story with you, stages ready-cut props on three depth planes, directs camera and music — and you can rearrange the set while it…

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 0 · Act 31 · Transact 0 · Score: Not yet scored

Tool inspector

theater_art_prompt

act imperative

Get a ready-to-use image-generation prompt for the art this show needs, then paste it into whatever can draw. Ask for one SHEET — a grid of separate pictures in a single image — because that is what piece_sheet cuts apart, and because one sheet comes back looking like one set rather than nine unrelated drawings. For a new play, use 'scenery' for separate trees, bushes, doors and other set pieces, and 'actors' for the full-body cast. Import both as cut-out pieces. A finished-looking scene cannot be rearranged or animated. The legacy 'backgrounds' kind can still make wide pictures for old plays, but new scenes use the open canvas and stage_create no longer accepts a backdrop. All are written in one house style so the cast and the set match. Brand and studio names in your topic are replaced with what they actually describe, and the reply says which. Ask for a FULL SHEET each time — 5 × 5 for actors and scenery, which is 25 pieces in one go. A set is made of a lot of small things, and generating them one at a time is the slowest possible way to build one. The exception is a sheet of BIG things — a throne, a door, a wall, a tree meant to fill the stage. Cells share the sheet's pixels, so 25 of them land around 250px each and look soft the moment one is drawn large; ask for columns 3, rows 3 and each piece gets two thirds again the size. Keep 5 × 5 for anything played small.

Page: /

Input schema

Property	Type	Required	Description
`kind`	string	yes	Use 'actors' for the cast or 'scenery' for separate set pieces. 'backgrounds' is for legacy plays; new scenes have no backdrop panel.
`topic`	string	no	What the play is about, in the words the person used — 'Little Red Riding Hood', 'a robot who loses a bolt'.
`columns`	number	no	Cells across, 1–5. Leave it alone: the defaults are 5 × 5 for actors and scenery — 25 pieces from one generation. The legacy backgrounds kind uses wide cells.
`rows`	number	no	Cells down, 1–5.
`shape`	string	no	The shape of one cell. Actors and scenery usually stay square; use wide or tall only when an individual cut-out needs that shape.
`subjects`	array	no	What goes in each cell, in reading order. Worth giving: the defaults are a generic folk tale and you know the story. Keep the same order when you pass labels to piece_sheet and every piece arrives named.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string",
      "enum": [
        "actors",
        "scenery",
        "backgrounds"
      ],
      "description": "Use 'actors' for the cast or 'scenery' for separate set pieces. 'backgrounds' is for legacy plays; new scenes have no backdrop panel."
    },
    "topic": {
      "type": "string",
      "description": "What the play is about, in the words the person used — 'Little Red Riding Hood', 'a robot who loses a bolt'."
    },
    "columns": {
      "type": "number",
      "description": "Cells across, 1–5. Leave it alone: the defaults are 5 × 5 for actors and scenery — 25 pieces from one generation. The legacy backgrounds kind uses wide cells."
    },
    "rows": {
      "type": "number",
      "description": "Cells down, 1–5."
    },
    "shape": {
      "type": "string",
      "enum": [
        "wide",
        "square",
        "tall"
      ],
      "description": "The shape of one cell. Actors and scenery usually stay square; use wide or tall only when an individual cut-out needs that shape."
    },
    "subjects": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "What goes in each cell, in reading order. Worth giving: the defaults are a generic folk tale and you know the story. Keep the same order when you pass labels to piece_sheet and every piece arrives named."
    }
  },
  "required": [
    "kind"
  ]
}

Similar websites

wfsim.app

A Warframe calculator that simulates the fight instead of estimating it — builder, simulator, optimizer. Every formula cites its source, and the golden tests ar…

live Unverified Media & Personal

101 tools A12 / Act89 / T0 Not yet scored Seen 2026-11-05

enemies_targets_list enemies_target_new enemies_target_copy enemies_target_open enemies_target_set

Inspect tools