failecho

Report a failed tool call to the network

report_tool_failure

Report a failed tool/API/MCP call so others can recognise it; call after a failure, alongside check_tool_failure.

PRIVACY: this is a shared network. Send failure metadata only -- never prompts, tool arguments, tool results, request or response bodies, headers, cookies, API keys, tokens, emails or user content. Error text is normalized server-side and the raw string discarded. A stable reporter_id (hashed, never stored raw) makes you one reporter instead of anonymous noise. Writes are rate limited per client.

Input Schema

TableJSON Schema

Name	Required	Description
`service`	Yes	The MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias.
`version`	No	Version of the service/tool.
`operation`	Yes	The tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'.
`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.

Changed28 schema fields changedSep 19, 2026
- removedInput schema / properties / error_code / anyOf
```
Removed value: -[
-  {
-    "maxLength": 32,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / error_code / default
```
Removed value: -null
```
- addedInput schema / properties / error_code / maxLength
```
Added value: +32
```
- addedInput schema / properties / error_code / type
```
Added value: +"string"
```
- removedInput schema / properties / error_message / anyOf
```
Removed value: -[
-  {
-    "maxLength": 2000,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / error_message / default
```
Removed value: -null
```
- addedInput schema / properties / error_message / maxLength
```
Added value: +2000
```
- addedInput schema / properties / error_message / type
```
Added value: +"string"
```
- removedInput schema / properties / error_type / anyOf
```
Removed value: -[
-  {
-    "maxLength": 64,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / error_type / default
```
Removed value: -null
```
- addedInput schema / properties / error_type / maxLength
```
Added value: +64
```
- addedInput schema / properties / error_type / type
```
Added value: +"string"
```
- removedInput schema / properties / latency_ms / anyOf
```
Removed value: -[
-  {
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / latency_ms / default
```
Removed value: -null
```
- addedInput schema / properties / latency_ms / minimum
```
Added value: +0
```
- addedInput schema / properties / latency_ms / type
```
Added value: +"integer"
```
- removedInput schema / properties / reporter_id / anyOf
```
Removed value: -[
-  {
-    "maxLength": 200,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / reporter_id / default
```
Removed value: -null
```
- addedInput schema / properties / reporter_id / maxLength
```
Added value: +200
```
- addedInput schema / properties / reporter_id / type
```
Added value: +"string"
```
- removedInput schema / properties / schema_hash / anyOf
```
Removed value: -[
-  {
-    "maxLength": 64,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / schema_hash / default
```
Removed value: -null
```
- addedInput schema / properties / schema_hash / maxLength
```
Added value: +64
```
- addedInput schema / properties / schema_hash / type
```
Added value: +"string"
```
- removedInput schema / properties / version / anyOf
```
Removed value: -[
-  {
-    "maxLength": 64,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / version / default
```
Removed value: -null
```
- addedInput schema / properties / version / maxLength
```
Added value: +64
```
- addedInput schema / properties / version / type
```
Added value: +"string"
```

Changed12 schema fields changedSep 17, 2026

removedInput schema / properties / error_code / title
```
Removed value: -"Error Code"
```
removedInput schema / properties / error_message / title
```
Removed value: -"Error Message"
```
removedInput schema / properties / error_type / title
```
Removed value: -"Error Type"
```
removedInput schema / properties / latency_ms / title
```
Removed value: -"Latency Ms"
```

changedInput schema / properties / operation / description

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

removedInput schema / properties / operation / title
```
Removed value: -"Operation"
```
removedInput schema / properties / reporter_id / title
```
Removed value: -"Reporter Id"
```
removedInput schema / properties / schema_hash / title
```
Removed value: -"Schema Hash"
```

changedInput schema / properties / service / description

Previous 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."New value: +"The MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias."

removedInput schema / properties / service / title
```
Removed value: -"Service"
```
removedInput schema / properties / version / title
```
Removed value: -"Version"
```

removedInput schema / title

Removed value: -"report_tool_failureArguments"

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

A3.9/5.0

Behavior5/5

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

The privacy paragraph adds substantial behavioral context beyond the sparse annotations: shared network, metadata-only policy, server-side normalization, hashed reporter_id, and per-client rate limiting. This is critical operational information that helps the agent use the tool safely and would not be derivable from the schema or annotations.

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?

Two tight paragraphs: the purpose is front-loaded in one sentence, and the privacy/behavior block is densely packed with essential exceptions. No filler, though the privacy section is long enough that it could be considered slightly heavy or combined.

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?

With an output schema present and 100% parameter coverage, the description provides the missing operational context: when to call, privacy boundaries, rate limiting, and identity hashing. It does not explain the response shape, but the output schema covers that. Overall adequate for a side-effectful reporting tool.

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 description coverage is 100%, so the baseline is 3. The description reinforces privacy constraints (e.g., no secrets in error_message) and the hashing behavior of reporter_id, but these are already present in the schema descriptions. It adds no new per-parameter semantics beyond the schema.

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?

States a specific verb and resource ('Report a failed tool/API/MCP call so others can recognise it') and gives clear context ('call after a failure'). It names a sibling (check_tool_failure) but does not explicitly contrast with report_tool_success or report_recovery_outcome, so it stops short of full differentiation.

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?

Explicitly says when to call it ('after a failure') and suggests a companion call ('alongside check_tool_failure'). However, it provides no guidance on when NOT to use it versus the other sibling tools, leaving some routing decisions to inference.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.