Skip to main content
Glama

Get node errors

get_td_node_errors
Read-only

Check a node or its sub-network for cook and compile errors, with an option to return grouped counts instead of the full list.

Instructions

Check a node (or its whole sub-network) for cook/compile errors and warnings. Pass summary:true for grouped counts instead of the full list.

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
pathYes
totalYes
errorsNo
by_typeNo
Behavior3/5

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

Annotations already declare readOnlyHint (safe read) and openWorldHint (tolerates missing resources). The description adds that the tool checks cook/compile errors and can return either full or summarized results, but this is largely derived from the parameter 'summary'. No additional behavioral traits (e.g., performance implications, caching) are disclosed.

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 two sentences: the first states the core purpose, the second adds a key parameter hint. No wasted words; front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 (not shown but indicated) and annotations, the description covers the essential behavior. It explains the two modes (full list vs summary) and the optional recursion. Missing is a note that the output schema exists, but the agent can infer the structure from it.

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?

The input schema has 100% description coverage, so baseline is 3. The description reinforces the summary parameter's effect but adds no new meaning beyond what the schema already provides for 'path' and 'recursive'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Check' and the resource 'node for errors/warnings', specifying the ability to check a sub-network. However, it does not distinguish from the sibling tool 'summarize_td_errors', which might be a separate tool for aggregated views, leaving potential confusion.

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

Usage Guidelines3/5

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

The description provides a usage hint for the summary parameter ('Pass summary:true for grouped counts'), but lacks guidance on when to prefer this tool over alternatives like 'summarize_td_errors'. No explicit when-to-use or when-not-to-use context is given.

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