Skip to main content
Glama

Find TouchDesigner nodes

find_td_nodes
Read-only

Search a TouchDesigner node network by name pattern or operator type, returning matching paths and count. Supports recursive search and wildcards.

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
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_pathYesThe network root the search ran under.
recursiveYesWhether descendants were searched, echoing the request.
countYesTotal nodes matched before `limit` truncation.
truncatedYesTrue if more nodes matched than `limit` returned.
pathsNopath_only mode: the matched node paths and nothing else.
matchesNoDefault mode: each matched node as {path, name, type}.
Behavior5/5

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

The description discloses read-only behavior, recursion default, and return structure. Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds context about search scope and output format, enhancing transparency without contradiction.

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 two sentences, front-loaded with key verb and purpose. Every sentence adds value: first states what and how, second gives usage guidance. No wasted words.

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 good annotations and an output schema implied, the description is complete. It covers purpose, behavior, return format, recursion, and ties to sibling tools, leaving no major gaps for an agent to correctly invoke this tool.

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% with detailed descriptions for each parameter, so the baseline is 3. The description adds overall context (e.g., patterns with wildcards, type as substring) but does not significantly extend individual parameter meanings beyond the 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?

The description uses a specific verb ('search') and resource ('nodes'), and explicitly states the method (by name pattern and/or operator type). It distinguishes itself from siblings by naming get_td_nodes and get_td_topology, making the purpose clear and unique.

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?

The description provides explicit guidance on when to use this tool vs. alternatives: 'Prefer this over get_td_nodes when...' and 'use get_td_topology when you also need the wiring between them.' This gives clear context and exclusions.

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