Skip to main content
Glama

Find TouchDesigner nodes

find_td_nodes
Read-only

Search a TouchDesigner network for nodes matching a name pattern or operator type, with recursive subtree search by default.

Instructions

Read-only: search a network for nodes by name pattern and/or operator type, recursively by default. Returns {count, truncated, matches/paths}. Prefer this over get_td_nodes when you are looking for specific nodes anywhere in a sub-tree (get_td_nodes only lists one COMP's direct children); use get_td_topology when you also need the wiring between them.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesTotal nodes matched before `limit` truncation.
pathsNopath_only mode: the matched node paths and nothing else.
matchesNoDefault mode: each matched node as {path, name, type}.
recursiveYesWhether descendants were searched, echoing the request.
truncatedYesTrue if more nodes matched than `limit` returned.
parent_pathYesThe network root the search ran under.
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, and description starts with 'Read-only'. Description adds return format {count, truncated, matches/paths} and recursion default, enhancing transparency 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?

Three sentences: purpose, return format, usage guidance. Every sentence is essential, no fluff, front-loaded with key information.

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?

With full schema coverage, annotations, and output schema, the description adds purpose, guidance, and return format. It is complete for an agent to understand and use the tool correctly.

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 has 100% coverage with detailed descriptions. Description mentions 'name pattern and/or operator type' and 'recursively by default', but adds limited new meaning beyond schema. Baseline 3 is appropriate.

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?

Description clearly states it searches for nodes by name pattern and/or operator type, recursively by default. It distinguishes from siblings get_td_nodes and get_td_topology, making purpose unmistakable.

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 advises preferring this over get_td_nodes for subtree searches and get_td_topology when wiring is needed. Provides clear when-to-use and when-not-to-use guidance.

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