Skip to main content
Glama

Get node flags & wiring (why-is-it-black inspector)

get_td_node_flags
Read-only

Identify operator flags and input wiring that cause blank or black outputs in TouchDesigner. Scan a node or subtree with optional problem filtering.

Instructions

Read-only: report each node's operator flags (bypass / render / display / lock / allowCooking / clone) plus index-aware input wiring, network position, color and comment — the signals that explain a black/blank output that a parameter dump hides. Scan one node or a subtree (recursive); set only_problems to surface just the ops whose flags or cook errors would suppress output. Returns structuredContent for code to process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFull path of the node to inspect, or the COMP whose children to scan when recursive is set.
recursiveNoAlso scan the immediate children (depth 1) of path. Use this on a container to diagnose its whole network in one round-trip.
only_problemsNoReturn only nodes whose flags or cook errors would suppress output: bypass on, allowCooking off, or a cook error present. Conservative — display/render are reported but never used to filter (they default off on many visible ops).
max_nodesNoCap the number of nodes scanned during a recursive subtree walk.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
scannedYes
nodesYes
probeNo
warningsYes
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint. The description adds context about what is reported (flags, wiring, etc.) and what is hidden (parameter dumps), providing behavioral transparency beyond annotations. 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?

Single, well-structured paragraph that leads with the main purpose and then clarifies parameters. Every sentence is informative and necessary. 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?

For a tool with 4 params, 100% schema coverage, and an output schema, the description covers the use case completely. It explains the diagnostic role, recursion behavior, and problem-filtering feature without needing to detail return values (handled by output schema).

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 coverage is 100%, so baseline is 3. The description adds meaning beyond schema by explaining the purpose of 'only_problems' in diagnostic context ('conservative — display/render are never used to filter'). Adds value without repeating 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 ('report') and clearly identifies the resource (node's operator flags, input wiring, position, color, comment) and the problem it solves (explaining black/blank output that parameter dumps hide). It distinguishes from siblings like get_td_node_parameters by contrasting what it reveals vs. hides.

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 states when to use recursive ('diagnose its whole network') and only_problems ('surface just the ops whose flags or cook errors would suppress output'). Implies alternative tools when detailed parameter info is needed. No guidance is missing.

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