failecho

Report a successful tool call to the network

report_tool_success

Report that a call SUCCEEDED. Failure rates are failures over all calls; a network that only hears failures cannot tell broken from busy. No error data -- service, operation, version, latency.

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'.
`latency_ms`	No	Observed call latency in milliseconds.
`reporter_id`	No	Optional stable agent id; hashed, never stored raw.
`schema_hash`	No	Short hash of the tool schema used.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 19, 2026
- 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"
```

Changed9 schema fields changedSep 17, 2026

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_successArguments"

Changed2 schema fields changedSep 11, 2026

changedInput schema / properties / operation / description

Previous value: -"Operation that succeeded."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

Behavior4/5

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

The annotations indicate no readOnly or idempotent hints, so the description must convey the behavioral impact. It states what to report (latency, service, operation) and what not to report (error data), adding context about the network's aggregation, which is beyond the annotation schema.

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 a single, tightly packed sentence followed by a short exclusion list. It front-loads the core purpose and adds critical context without unnecessary fluff. Every sentence earns its place.

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 tool has an output schema and high schema coverage, the description covers the necessary context for calling it. It explains the rationale for reporting successes and what to exclude (error data), but could have been more explicit about when to use it versus report_tool_failure. Minor gap.

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 baseline is 3. The description adds extra guidance on the 'service' (server's own name vs client alias) and 'operation' (server naming), which enriches the parameter meanings. This extra semantic guidance justifies a 4.

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 verb 'Report' and the resource 'a call SUCCEEDED', and explicitly contrasts with failure reporting. It distinguishes from siblings like report_tool_failure by defining the success event and what data to exclude.

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 explicitly frames the network's failure-rate logic, saying a network that only hears failures cannot tell broken from busy, which guides when to call this tool to report successes. It does not name siblings directly but the context makes the usage clear.

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.