failecho

Report a failed tool call to the network

report_tool_failure

Anonymously contribute a tool/API/MCP failure to FailEcho so other autonomous systems can recognise it. Call this whenever a tool call fails, after (or alongside) check_tool_failure.

PRIVACY -- this is a shared public network. Send failure metadata ONLY. Never include prompts, model messages, tool arguments, tool results, request or response bodies, HTTP headers, cookies, API keys, tokens, customer names, emails or any user content. The error message is normalized server-side (numbers, UUIDs, emails, URLs, IPs and tokens replaced with placeholders; credential-shaped substrings redacted) and the raw text is discarded, but that is a safety net, not a licence to send sensitive data.

Pass a stable reporter_id if you can: it is salted and hashed before storage, is never stored raw, and lets the network count you as one independent reporter instead of anonymous noise. Writes are rate limited per client.

Input Schema

TableJSON Schema

Name	Required	Description
`service`	Yes	What was called, named the way other agents will name it: an MCP server's own name (the one it reports in serverInfo.name), or an HTTP API's host, e.g. 'api.github.com'. Not your client's local alias for it.
`version`	No	Version of the service/tool.
`operation`	Yes	The tool or endpoint exactly as the server defines it, e.g. 'create_issue' -- without client prefixes such as 'mcp__github__'.
`error_code`	No	Protocol/vendor code, e.g. '422'.
`error_type`	No	Short failure class, e.g. 'validation_error'.
`latency_ms`	No	Observed call latency in milliseconds.
`reporter_id`	No	Optional stable identifier for your agent. Salted and hashed on arrival; never stored raw.
`schema_hash`	No	Short hash of the tool schema used.
`error_message`	No	Error text. Normalized before storage; no secrets please.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / operation / description

Previous value: -"Operation that failed."New value: +"The tool or endpoint exactly as the server defines it, e.g. 'create_issue' -- without client prefixes such as 'mcp__github__'."

changedInput schema / properties / service / description

Previous value: -"Tool/service identifier."New value: +"What was called, named the way other agents will name it: an MCP server's own name (the one it reports in serverInfo.name), or an HTTP API's host, e.g. 'api.github.com'. Not your client's local alias for it."

First observedSep 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses anonymous public contribution, server-side normalization of error text, discarding of raw text, salted-hashed reporter_id storage, per-client rate limits, and what must never be sent. These are exactly the traits an agent needs before invoking a write to a shared network.

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?

Front-loaded with purpose, then usage, then privacy, then parameter notes — a sensible order. The privacy paragraph is long but each clause (banned categories, server-side normalization limits, the 'safety net, not a licence' caveat) earns its place; still, the block could be tightened.

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?

9 parameters, 2 required, an output schema present (so return values need no explanation) and no annotations — the description fills the gaps that matter: privacy boundaries, rate limiting, normalization behavior, and the identity semantics of reporter_id. An agent has everything needed to call this 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 description coverage is 100%, so the baseline is 3; however the description adds meaning beyond the schema by explaining the purpose of reporter_id (salted/hashed, counts you as one independent reporter rather than anonymous noise), the normalization applied to error_message, and the privacy constraints on all fields.

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?

States a specific verb (anonymously contribute) and resource (a tool/API/MCP failure to FailEcho) plus the benefit to other agents. It is clearly separable from the sibling check_tool_failure, which it names as a companion query rather than a duplicate.

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 trigger is explicit: 'Call this whenever a tool call fails, after (or alongside) check_tool_failure.' That gives a clear condition and ordering relative to one sibling, but it never states when NOT to use it or how it differs from report_tool_success / report_recovery_outcome, so the routing guidance is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All failecho tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.