Skip to main content
Glama

List TouchDesigner nodes

get_td_nodes
Read-only

List direct child nodes of a TouchDesigner COMP. Supports filtering by name pattern, detail level, and limiting results.

Instructions

List the direct child nodes of a COMP. Defaults to a compact summary (count + type breakdown + sample paths); pass detail_level:"full" or path_only:true for the complete list, and pattern to filter by name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent COMP whose direct children should be listed./project1
patternNoCase-insensitive filter on node name/path. Supports '*' wildcards (e.g. 'text*', '*noise*').
path_onlyNoReturn only the list of node paths, dropping type/name.
limitNoCap the number of nodes returned.
detail_levelNo'summary' (default) returns a count, a type breakdown and the first few paths; 'full' returns every node. Use 'full' (or path_only) when you need the complete list.summary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathYes
countYes
detail_levelYes
truncatedYes
by_typeNo
sampleNo
pathsNo
nodesNo
hintNo
Behavior4/5

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

Annotations declare readOnlyHint:true and openWorldHint:true, which already convey safety and potential variation. The description adds behavioral details: default to compact summary, options for full listing or path-only, and pattern filtering. This provides useful context beyond 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?

The description is a single, front-loaded sentence that efficiently conveys the core action and key options. Every word serves a purpose; no redundancy or filler.

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 tool has 5 parameters, all optional, and an output schema exists, the description covers the essential behaviors (listing children, summary format, filtering, limiting). It omits no critical details for an agent to use the tool correctly.

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?

Schema covers 100% of parameters with descriptions. The description synthesizes key parameter behaviors (summary vs. full, pattern with wildcards, limit) and explains the enum values, adding clarity tailored to the tool's use.

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 verb 'List' and the resource 'direct child nodes of a COMP'. It distinguishes from sibling tools like find_td_nodes (recursive search) and get_td_node_parameters (node parameters).

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 explains when to use the default summary vs. passing detail_level:'full' or path_only:true, and how to filter with pattern. It lacks explicit guidance on when not to use this tool (e.g., for recursive search), but the context implies it's for direct children only.

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/Pantani/tdmcp'

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