Skip to main content
Glama

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

get_td_node_flags
Read-only

Inspect operator flags and input wiring to diagnose blank or black output. Scan a single node or a subtree recursively, or filter with only_problems to list nodes suppressing output.

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.
max_nodesNoCap the number of nodes scanned during a recursive subtree walk.
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).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
nodesYes
probeNo
scannedYes
warningsYes
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 behavior beyond this: it enumerates the specific flag and wiring data returned, explains the recursive subtree scanning, and notes the conservative filtering behavior of only_problems. It also mentions structuredContent for code processing. This goes beyond merely repeating 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?

The description is three sentences, front-loaded with the core purpose and read-only guarantee. It packs details about flags, wiring, position, color, comment, recursive scanning, and the only_problems filter without any filler or redundancies.

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 presence of an output schema and 100% parameter coverage, the description fully covers the tool's purpose, usage patterns, and behavioral nuances. It explains what the tool returns (flags, wiring, position, color, comment), how to scan subtrees, and how to focus on problem nodes, making it complete for an agent to select and invoke 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 description coverage is 100%, so the baseline is 3. The description mentions recursive and only_problems but essentially paraphrases the schema's own descriptions, adding no net-new parameter meaning. It does not add syntax or formatting details beyond what the schema already provides. Therefore, the description adds marginal value over 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 states a specific verb ('report') and resource ('each node's operator flags... plus index-aware input wiring, network position, color and comment'). The title adds a clear diagnostic purpose ('why-is-it-black inspector'), and the content distinguishes it from sibling tools like get_td_node_parameters or get_td_topology by focusing on output-suppression signals.

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

Usage Guidelines4/5

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

The description clarifies when this tool is valuable: 'the signals that explain a black/blank output that a parameter dump hides.' It also explains the recursive scan mode and the only_problems filter. However, it does not explicitly name alternatives or state when not to use it, stopping short of a full when/when-not comparison.

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/lucasmaher-hash/touch-designer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server