Skip to main content
Glama

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

get_td_node_flags
Read-only

Inspect node operator flags and wiring to diagnose blank outputs. Optionally filter to only problematic nodes with suppressed 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.
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?

The description confirms read-only behavior (consistent with readOnlyHint=true) and adds specific details: what flags are reported, the affect of only_problems, and that it returns structuredContent. No contradiction with annotations. The openWorldHint is not addressed but also not contradicted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-organized paragraph that front-loads the core purpose and then details parameters. It is informative without unnecessary words, though slightly dense.

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 tool's moderate complexity (4 parameters, output schema exists), the description covers all essential aspects: purpose, usage, behavior, and parameter roles. No critical gaps remain for an agent to use it correctly.

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 descriptions already exist for all parameters. The tool description adds useful context beyond the schema (e.g., explaining the purpose of only_problems and recursive). This enriches the agent's understanding without redundancy.

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 specifies a precise verb ('report'), a specific resource ('node flags & wiring'), and the context ('explain black/blank output'). It clearly distinguishes from sibling tools like get_td_node_parameters by focusing on flags and wiring rather than parameter values.

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 provides clear usage guidance: scan one node or subtree (recursive) and filter with only_problems. It mentions the alternative 'parameter dump' but does not explicitly exclude other tools. The context is sufficient for an agent to decide when to use this tool.

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