Skip to main content
Glama

List TouchDesigner nodes

get_td_nodes
Read-only

List the direct child nodes of a TouchDesigner COMP without recursion. Get a compact summary or full list, optionally filtered by name pattern.

Instructions

Read-only: list the DIRECT child nodes of one 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. Returns {count, by_type/sample or paths/nodes}. Use this to browse one level; use find_td_nodes to search recursively and by operator type, or get_td_topology when you also need the connections between nodes.

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_pathYesThe parent COMP whose children were listed.
countYesNumber of children matched (before any limit truncation).
detail_levelYesWhich detail level produced this result, echoing the request.
truncatedYesTrue if `limit` cut the list short of the full match count.
by_typeNoSummary mode: count of matched nodes per operator type.
sampleNoSummary mode: paths of the first few matched nodes.
pathsNopath_only mode: the matched node paths and nothing else.
nodesNoFull mode: every matched node as {path, name, type}.
hintNoSummary mode: note that the list was sampled, with how to get all of it.
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context: default compact summary, return format (count, by_type/sample, paths/nodes), and behavior of pattern with wildcards. 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?

Two sentences, no waste. First sentence states purpose, second provides usage guidance and alternative tools. Front-loaded and efficient.

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 5 parameters (all described in schema), an output schema, and moderate complexity, the description covers the tool's behavior, options, and relationships to siblings. No missing critical information.

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 baseline is 3. The description clarifies the summary vs full distinction and when to use path_only, but these are already implied in the schema enum. Does not add substantial new meaning beyond 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?

Clearly states 'list the DIRECT child nodes of one COMP' with a specific verb and resource. Distinguishes from siblings by naming find_td_nodes (recursive) and get_td_topology (connections). The scope 'one level' is explicit.

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

Usage Guidelines5/5

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

Provides explicit when-to-use: 'Use this to browse one level; use find_td_nodes to search recursively... or get_td_topology when you also need the connections.' Also explains default summary mode and options detail_level / path_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