Skip to main content
Glama

Get node errors

get_td_node_errors
Read-only

Check a TouchDesigner node or its sub-network for cook/compile errors and warnings, returning a full list or grouped counts 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.
summaryNoReturn only counts grouped by error type instead of the full error list.
recursiveNoIf true, check the whole network under `path`; otherwise just that node.

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 and destructiveHint=false, and the description aligns with 'Read-only'. It adds behavioral context beyond annotations: explains recursive sub-network traversal, summary mode, and the return structure. This enriches understanding without contradicting annotations, though it doesn't detail performance implications or edge cases.

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, each adding distinct value: the read-only nature and scope, the summary grouping behavior, and the alternative tool for large networks. Front-loaded with 'Read-only' and the primary purpose; no filler.

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 an output schema present, the description is complete for the tool's complexity: covers usage with recursive and summary, return format, and a specific alternative tool for large networks. It addresses all key aspects an agent would need to invoke 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% and descriptions are provided for all parameters. The tool description adds value by explaining the combined effect of recursive and summary, and clarifies the return format ({total, errors[] or by_type}), which enriches the schema definitions 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 clearly states the tool reads node errors and warnings, with a specific verb ('check') and resource ('node or sub-network'). It distinguishes itself from the sibling summarize_td_errors by mentioning the alternative for large networks, making its purpose and scope unmistakable.

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 says to prefer summarize_td_errors for large networks, providing an alternative and the reason (clustering by shared cause, pointing at worst-offending nodes). Also describes when to use recursive and summary parameters, giving clear context for tool selection.

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