Skip to main content
Glama

Find TouchDesigner nodes

find_td_nodes
Read-only

Search a network for nodes by name pattern and operator type. Returns matching paths or full details, recursively by default.

Instructions

Search a network for nodes by name pattern and/or operator type. Recursive by default; pass path_only:true for a compact path list. Prefer this over get_td_nodes when you are looking for specific nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoWhere to search from./project1
patternNoCase-insensitive name/path filter with '*' wildcards (e.g. 'text*', '*noise*').
typeNoCase-insensitive operator-type substring (e.g. 'TOP', 'noise').
recursiveNoSearch the whole sub-network (true) or only direct children (false).
path_onlyNoReturn only matching paths.
limitNoMax matches to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathYes
recursiveYes
countYes
truncatedYes
pathsNo
matchesNo
Behavior4/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description adds behavioral details like recursion by default and the ability to return compact paths. It does not contradict 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?

Two concise sentences with no wasted words, front-loaded with core purpose.

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 6 parameters (all optional, well-described in schema) and the presence of output schema, the description fully covers the tool's usage context and behavior.

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%, so description adds little new semantic meaning. It briefly mentions pattern, type, recursion, and path_only, but the schema already describes them adequately.

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 it searches for nodes by name pattern and/or operator type, and distinguishes itself from sibling 'get_td_nodes' by advising preference for specific nodes.

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?

Explicitly recommends using this over 'get_td_nodes' when looking for specific nodes, and mentions default recursion and the path_only option.

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