Skip to main content
Glama
axysar

touchdesigner-agent-mcp

by axysar

get_td_nodes

Read-onlyIdempotent

List child operators in a TouchDesigner network under a specified parent path, filtered by an optional name pattern. Returns node details including ID, name, path, and type.

Instructions

List child operators under a path, optionally filtered by a name pattern.

Returns {nodes: [{id, name, path, opType, properties}]}. Set include_properties=true only when you need values — the light default is faster for large networks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentNoParent operator path (e.g. '/project1')./
patternNoName glob to filter children (e.g. 'text*').
response_formatNoOutput format: 'json' (default) or 'markdown'.json
include_propertiesNoInclude full parameter sets (slower). Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds a key behavioral insight: performance trade-off when setting include_properties=true. It also clarifies the return format. No contradictions.

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?

Only two sentences: concise, front-loaded with main purpose, then adds performance advice. Every word earns its place.

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?

The description combined with annotations and schema provides a complete picture: purpose, return format, key parameter guidance, safety profile. With output schema available (not shown but indicated), no additional explanation of return values is needed.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for all parameters. The description adds minimal extra context beyond the schema (performance note for include_properties). Baseline of 3 is appropriate since the schema already carries the burden.

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 lists child operators under a path, with a specific verb ('List') and resource ('child operators'). It immediately distinguishes from sibling tools like create, delete, or execute.

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

Usage Guidelines4/5

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

The description implies usage for browsing operator hierarchy, but does not explicitly state when to use this tool over siblings like get_td_info or get_td_class_details. However, the combination of name and description makes the purpose clear enough.

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/axysar/touchdesigner-agent-mcp'

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