Skip to main content
Glama

Plan a visual from a description

plan_visual
Read-only

Generate a read-only TouchDesigner build plan from a visual description. Use deterministic planning by default, or opt into a bounded LLM plan with validated recipes and operators.

Instructions

Turn a visual description into a read-only build plan. The deterministic planner remains the default and creates nothing. Set planner='llm' to opt into one bounded completion grounded in compact editor/project/recipe/operator evidence; every suggested tool, recipe and operator is validated, and any unavailable or invalid LLM path falls back deterministically without mutating TouchDesigner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plannerNoUse the deterministic keyword planner (default), or explicitly request one bounded, grounded LLM completion with deterministic fallback.deterministic
root_pathNoOptional TouchDesigner root used only for bounded read-only grounding in planner='llm'.
descriptionYesNatural-language description of the visual you want.
llm_timeout_msNoBound the single LLM completion to 1000-10000 ms.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYes
warningsYes
groundingYes
operatorsYes
recipe_idYes
planner_usedYes
interpretationYes
schema_versionYes
fallback_reasonYes
recommended_toolYes
planner_requestedYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes beyond the annotations by detailing exactly what happens: 'every suggested tool, recipe and operator is validated,' and 'any unavailable or invalid LLM path falls back deterministically without mutating TouchDesigner.' This discloses fallback behavior and safety guarantees, adding substantial value beyond the readOnlyHint/destructiveHint annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences pack all necessary information: purpose, default behavior, and LLM option details. There is no redundancy or filler; each sentence adds a distinct piece of information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and full parameter descriptions, the description is highly complete. It covers purpose, safety (read-only), planner behavior, and fallback mechanism, leaving no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers 100% of parameters with descriptions, so baseline is 3. The description adds meaning to the 'planner' parameter by explaining the difference between deterministic and LLM modes, including the bounded completion and fallback behavior, which is not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Turn a visual description into a read-only build plan.' The verb 'turn' plus the resource 'visual description' make the action explicit, and 'read-only build plan' distinguishes it from execution-oriented sibling tools that create or modify TouchDesigner nodes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context that this is a planning tool that 'creates nothing,' which implies it should be used before actual node creation. However, it does not explicitly name alternative tools or state when not to use it, leaving the comparison to siblings implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucasmaher-hash/touch-designer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server