Skip to main content
Glama

Get node errors

get_td_node_errors
Read-only

Check a TouchDesigner node or its sub-network for errors and warnings. Optionally get summary counts grouped by error type.

Instructions

Read-only: check one node (or, with recursive:true, its whole sub-network) for cook/compile errors and warnings. Pass summary:true for grouped counts instead of the full list. Returns {total, errors[] or by_type}. For a large network prefer summarize_td_errors, which clusters errors by shared cause and points at the worst-offending nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFull path of the node (or network root) to check for errors.
recursiveNoIf true, check the whole network under `path`; otherwise just that node.
summaryNoReturn only counts grouped by error type instead of the full error list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe node or network root that was checked, echoing the request.
totalYesTotal number of errors/warnings found (0 means clean).
errorsNoFull mode: each error/warning with its node path, type and message.
by_typeNosummary mode: count of errors grouped by error type.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description adds return structure {total, errors[] or by_type} and effects of recursive and summary flags, going beyond annotations 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?

Three sentences that are front-loaded with the main action, no unnecessary words. Every sentence provides essential 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?

Given 3 parameters, annotations, and output schema, the description fully covers usage, return structure, and alternatives. It leaves no gaps.

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% with good descriptions. The description further clarifies the effect of summary=true and recursive flag, and explains the output format, adding value beyond 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 clearly states it checks a node for cook/compile errors and warnings, with scope control via recursive flag. It distinguishes itself from sibling summarize_td_errors by noting when to prefer that alternative.

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 mentions using summary=true for grouped counts and advises using summarize_td_errors for large networks, providing 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