Skip to main content
Glama

Report how a call to an MCP server went (7Maps)

report_road

Use 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

NameRequiredDescriptionDefault
msNoDuration in ms
okYesDid it do what you needed
failNoWhy it failed
toolNoTool called
serverYesServer called (URL or registry name)
surpriseNoSide effect you did not ask for
task_typeNoOptional: kind of work (only the category is kept)
tools_hashNotool_list_hash, computed as 7Maps does
agent_modelNoOptional: your model id, e.g. "claude-sonnet-5-5". Anonymous
charged_usdNoCharged in USD
result_tokensNoResult size in tokens
matched_descriptionNoResult matched the tool description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / agent_model / description
      Previous value: -"Optional: the model you run on, for example \"claude-sonnet-5-5\", \"gpt-5\", \"llama3.2:3b\". Anonymous; it helps 7Maps learn which servers work for which models"New value: +"Optional: your model id, e.g. \"claude-sonnet-5-5\". Anonymous"
    • changedInput schema / properties / charged_usd / description
      Previous value: -"What the server charged, if anything"New value: +"Charged in USD"
    • changedInput schema / properties / fail / description
      Previous value: -"If it failed: unreachable, auth, args, server_error, timeout, rate_limited or wrong_result"New value: +"Why it failed"
    • changedInput schema / properties / matched_description / description
      Previous value: -"Whether the result matched what the tool description promised"New value: +"Result matched the tool description"
    • changedInput schema / properties / ms / description
      Previous value: -"How long the call took, in milliseconds"New value: +"Duration in ms"
    • changedInput schema / properties / ok / description
      Previous value: -"Whether the call did what you needed"New value: +"Did it do what you needed"
    • changedInput schema / properties / result_tokens / description
      Previous value: -"About how many tokens the result was"New value: +"Result size in tokens"
    • changedInput schema / properties / server / description
      Previous value: -"The MCP server you called (URL or registry name)"New value: +"Server called (URL or registry name)"
    • changedInput schema / properties / surprise / description
      Previous value: -"Anything the tool did that you did not ask for"New value: +"Side effect you did not ask for"
    • changedInput schema / properties / task_type / description
      Previous value: -"Optional: the kind of work you are doing right now. Only this category is kept, never your task text"New value: +"Optional: kind of work (only the category is kept)"
    • changedInput schema / properties / tool / description
      Previous value: -"The tool you called"New value: +"Tool called"
    • changedInput schema / properties / tools_hash / description
      Previous value: -"The tool_list_hash of the tool list you received, if you computed it as 7Maps does"New value: +"tool_list_hash, computed as 7Maps does"
  2. Changed2 schema fields changed
    • addedInput schema / properties / agent_model
      Added value: +{
      +  "description": "Optional: the model you run on, for example \"claude-sonnet-5-5\", \"gpt-5\", \"llama3.2:3b\". Anonymous; it helps 7Maps learn which servers work for which models",
      +  "maxLength": 80,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_type
      Added value: +{
      +  "description": "Optional: the kind of work you are doing right now. Only this category is kept, never your task text",
      +  "enum": [
      +    "coding",
      +    "research",
      +    "data",
      +    "communication",
      +    "commerce",
      +    "devops",
      +    "content",
      +    "personal_assistant",
      +    "testing",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say readOnlyHint=false, idempotentHint=false, destructiveHint=false) by disclosing the downstream consequence — reports aggregate into the server's rating and, after 7Maps verification, become incident alerts seen by every agent. It also discloses privacy handling (task_type keeps only the category, agent_model is anonymous), that only fixed fields are accepted with no open text, and that there is no charge. That is exactly the kind of behavioral context annotations cannot carry.

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?

Front-loaded with the trigger ('Use this after calling a tool...'), then why it matters, then the alternative channel and cost. Every sentence carries information: intent, field constraints, downstream effect, and the last_trip reuse path. No filler or repetition.

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?

For a 12-parameter write tool with no output schema, the description covers timing, field constraints, anonymity, cost, and the downstream use of the data. It does not say what the call returns or whether the report can be corrected or withdrawn later, which would matter for an agent filing a negative report about a server.

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, but the description adds real meaning by tying the fields together into a narrative of what is being reported: whether it worked, why not, how long it took, whether the result matched the description, and anything it did that was not asked for. That maps the 12 fields to five distinct questions an agent should be able to answer, which the per-property descriptions alone do not convey.

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 concrete verb and resource: report how a call to an MCP server tool went, with a parenthetical narrowing it to servers 7Maps pointed you to. An agent can tell this is a post-call feedback tool, though it doesn't explicitly distinguish itself from the sibling my_server_report, which an agent might reasonably confuse it with.

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?

Clear trigger condition: 'Use this after calling a tool on an MCP server.' It also explains an alternate channel for the same data (passing the fields as last_trip on the next 7Maps call), which helps an agent decide between reporting now versus batching. There is no explicit when-not or named alternative tool, keeping it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources