Skip to main content
Glama

td_get_nodes

Read-onlyIdempotent

List child operators (nodes) under a network path in TouchDesigner. Supports filtering by operator type or family, pagination, and parameter inclusion.

Instructions

List the child operators (nodes) directly under a network path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoAbsolute path to a COMP node whose children to list (e.g. '/', '/project1', '/project1/myComp')/
typeNoFilter by specific operator type (e.g. 'noiseTOP', 'waveCHOP', 'textDAT')
limitNoMax number of nodes to return
familyNoFilter by operator family: TOP, CHOP, SOP, DAT, COMP, MAT, or PANEL
offsetNoPagination offset
include_paramsNoIf true, include all parameters for each node (slower for large networks)
response_formatNoOutput formatjson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds no behavioral detail beyond the basic operation, consistent with 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?

Single sentence, no wasted words, front-loaded with action. Extremely concise.

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

Completeness3/5

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

Adequate given the rich schema and output schema, but the minimal description may not fully inform a new user about filtering, pagination, and other capabilities. Could be more complete.

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 description coverage is 100%, so all 7 parameters are documented in the schema. The description adds no additional parameter information beyond what the schema provides.

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

Purpose4/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 network path, using specific verb 'List' and resource 'child operators (nodes)'. It is distinctive from siblings like td_search_nodes or td_get_node_detail, though it doesn't explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like td_search_nodes or td_create_node. Lacks when-to-use or when-not-to-use context.

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/dreamrec/TDPilot'

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