Skip to main content
Glama

Summarize network errors

summarize_td_errors
Read-only

Collect errors across a network, cluster by message, type, or parent, and identify worst-offending nodes with investigation suggestions. Use for network-wide triage instead of reading every node's errors individually.

Instructions

Read-only: collect errors across a network and cluster them by message, type, or parent container, with the worst-offending nodes and a suggested order to investigate. Returns {total, groups[], suggestions[]}. Use this for network-wide triage instead of reading every node's errors one by one; use get_td_node_errors when you just want the raw error list for one node or sub-tree.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoNetwork root to collect errors under./project1
group_byNoHow to cluster errors: by exact message, by error type, or by parent container (to find a common upstream cause).message

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe network root errors were collected under, echoing the request.
totalYesTotal number of errors found across the network (0 means clean).
group_byYesHow the errors were clustered, echoing the request.
groupsYesError clusters, largest first; fixing a big cluster's cause clears it at once.
suggestionsYesPlain-language next steps, e.g. the common cause and which nodes to check first.
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 reinforces this by stating 'read-only' and adds behavioral context about clustering, worst-offending nodes, and suggested investigation order. No hidden side effects are omitted.

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, front-loaded with 'read-only', and provides all necessary information without any wordiness. Every sentence adds value.

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?

The tool is simple with only two parameters, has output schema hinted, annotations cover safety, and description gives usage guidance. No gaps for an AI 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 coverage is 100% with both path and group_by parameters fully described. The description adds no additional parameter details beyond what schema provides, but the schema alone is sufficient. Baseline 3 applies.

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 collects errors across a network and clusters them by message, type, or parent container, returning a structured summary. It explicitly distinguishes from the sibling tool get_td_node_errors by specifying network-wide triage vs. per-node raw list.

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?

The description provides explicit when-to-use (network-wide triage) and when-not-to-use (raw error list for one node, use get_td_node_errors instead). This leaves no ambiguity.

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