Skip to main content
Glama

Condition of an MCP server before connecting (7Maps)

road_conditions
Read-onlyIdempotent

Use this before connecting to or calling any MCP server you have not used today, or installing a local one: is it up, does it need sign-in, how fast it answers, how many tools are read-only, need approval or are high risk (estimated from public tool descriptions), when its tools last changed and the chance the next call works (daily checks, 30 days of history). For an npm or PyPI server: version, maintainers, install scripts and supply-chain changes. Paid per check (see list_paid_tools). Reads the map only; never calls the server.

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>"
    },
    "name": "road_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesThe server URL (https://mcp.example.com/mcp), its official registry name, or npm:<package> / pypi:<package> for a server that runs locally
last_tripNoOptional: how your previous call to a server 7Maps named went
task_typeNoOptional: kind of work (only the category is kept)
agent_modelNoOptional: your model id, e.g. "claude-sonnet-5-5". Anonymous
license_keyNo7IT plan license key; else pay per call (x402)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 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 / last_trip / description
      Previous value: -"Optional: how your previous call to an MCP server went (one 7Maps named), as the last 7Maps answer shows."New value: +"Optional: how your previous call to a server 7Maps named went"
    • changedInput schema / properties / last_trip / properties / charged_usd / description
      Previous value: -"What the server charged, if anything"New value: +"Charged in USD"
    • changedInput schema / properties / last_trip / 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 / last_trip / 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 / last_trip / properties / ms / description
      Previous value: -"How long the call took, in milliseconds"New value: +"Duration in ms"
    • changedInput schema / properties / last_trip / properties / ok / description
      Previous value: -"Whether the call did what you needed"New value: +"Did it do what you needed"
    • changedInput schema / properties / last_trip / properties / result_tokens / description
      Previous value: -"About how many tokens the result was"New value: +"Result size in tokens"
    • changedInput schema / properties / last_trip / 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 / last_trip / 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 / last_trip / properties / tool / description
      Previous value: -"The tool you called"New value: +"Tool called"
    • changedInput schema / properties / last_trip / 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"
    • changedInput schema / properties / license_key / description
      Previous value: -"A 7IT monthly plan license key, if you have one; otherwise pay per call with x402"New value: +"7IT plan license key; else pay per call (x402)"
    • 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)"
  2. Changed1 schema field changed
    • changedInput schema / properties / last_trip / description
      Previous value: -"Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge."New value: +"Optional: how your previous call to an MCP server went (one 7Maps named), as the last 7Maps answer shows."
  3. 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"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / last_trip / description
      Previous value: -"Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; 5 accepted reports from a paying wallet earn 1 call at no charge."New value: +"Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; accepted reports from a paying wallet earn calls at no charge."
  5. Changed1 schema field changed
    • changedInput schema / properties / last_trip / description
      Previous value: -"Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; 5 accepted reports from a paying wallet earn 1 free call."New value: +"Optional: how your last call to an MCP server went (the one 7Maps pointed you to). It keeps the map honest; 5 accepted reports from a paying wallet earn 1 call at no charge."
  6. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description stays consistent while adding real context: it 'Reads the map only; never calls the server', is paid per check, draws on daily checks over 30 days of history, and its risk figures are only 'estimated from public tool descriptions' — an important accuracy caveat. A small gap is that it does not state cost magnitude or latency characteristics of the check itself.

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?

The trigger condition is front-loaded in the first clause, and the dense enumeration of returned signals is compact rather than padded. The single run-on construction packs a lot into one block and could be split, but nearly every clause carries information an agent needs.

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 read-only, five-parameter tool with a nested optional last_trip object and no output schema, the description covers the important unknowns: what is checked, freshness of the data, estimation caveats, cost model, and the fact that the target server is never contacted. It could say more about how last_trip improves results, but overall it is sufficient to call correctly.

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 schema already explains server formats, last_trip fields, task_type enums, and license_key. The description adds only modest value beyond that, mainly clarifying the accepted server identifier forms (URL, registry name, npm:/pypi:) and the npm/PyPI supply-chain output. Baseline 3 is appropriate since the schema carries the parameter burden.

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?

The description concretely enumerates what the tool reports: uptime, sign-in requirements, latency, tool risk breakdown, last tool change date, success probability, and package supply-chain details for npm/PyPI servers. That is far beyond a restatement of the name. It stops short of naming overlapping siblings (e.g., preflight, tool_card, resolve), so an agent must infer differentiation itself.

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?

It gives a sharp trigger condition: 'before connecting to or calling any MCP server you have not used today, or installing a local one.' The 'not used today' clause implicitly excludes repeat use, and it routes cost questions to list_paid_tools. It does not explicitly contrast with adjacent checks like preflight or tool_card, leaving some selection ambiguity.

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