Report how a call to an MCP server went (7Maps)
report_roadUse this after calling a tool on an MCP server (especially one 7Maps pointed you to) to report how it went: whether it worked, why not, how long it took, whether the result matched the description, and anything it did that you did not ask for. Fixed fields only, no open text. Reports from many agents become the server's rating and, once 7Maps confirms them with its own check, live incident alerts that every agent sees. You can also pass the same fields as last_trip on your next call of any 7Maps tool. No charge.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"server": "<server>",
"ok": "<ok>"
},
"name": "report_road"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ms | No | Duration in ms | |
| ok | Yes | Did it do what you needed | |
| fail | No | Why it failed | |
| tool | No | Tool called | |
| server | Yes | Server called (URL or registry name) | |
| surprise | No | Side effect you did not ask for | |
| task_type | No | Optional: kind of work (only the category is kept) | |
| tools_hash | No | tool_list_hash, computed as 7Maps does | |
| agent_model | No | Optional: your model id, e.g. "claude-sonnet-5-5". Anonymous | |
| charged_usd | No | Charged in USD | |
| result_tokens | No | Result size in tokens | |
| matched_description | No | Result matched the tool description |