Skip to main content
Glama

What changed on my MCP servers (7Maps)

changes_since
Read-onlyIdempotent

Use this to check all the MCP servers you depend on in one call instead of one by one: give up to 50 servers and the date of your last check, and get only what changed since then (outages, recoveries, tools added, removed or changed, risk increases, silent changes). Most answers are "nothing changed". Which to use: changes_since for up to 50 servers at once; watch for one server; verify_lock against a saved lock. Paid per call (see list_paid_tools). Reads the map only.

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": {
      "servers": "<servers>",
      "since": "<since>"
    },
    "name": "changes_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesDate of your last check (YYYY-MM-DD); up to 30 days back
serversYesServer URLs or official registry names
last_tripNoOptional: how your previous call to a server 7Maps named went
license_keyNo7IT plan license key; else pay per call (x402)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • 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)"
  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. 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."
  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 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."
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description reinforces with 'Reads the map only.' Beyond that it discloses two non-obvious behaviors: billing per call and the expectation that most responses are 'nothing changed,' which shapes how an agent should interpret empty results. It does not discuss failure modes for unrecognized server names or the 30-day lookback limit (left to the schema), keeping it below a 5.

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?

Front-loads the core capability and keeps the call-count and cost caveats in a compact parenthetical; the 'Which to use:' block is scannable. The telegraphic fragment style ('watch for one server') is efficient but slightly terse, and the long change-type list competes for attention.

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 no output schema, the description carries the return-value burden and does so by enumerating the delta categories and warning that most responses are empty. For a paid, 4-parameter tool with one nested object, the remaining gap is what an unknown or invalid server entry yields — useful but not blocking.

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 documents since, servers, last_trip, and license_key, including the 50-item cap and 30-day window restated in the description. The description adds no syntax or format detail for the nested last_trip feedback object, so it neither compensates for nor extends the schema. Baseline 3 applies.

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?

States a specific verb and resource (check MCP servers you depend on) plus the exact scope of a single call: up to 50 servers with a since-date, returning only deltas. It immediately names what the deltas are (outages, recoveries, tool changes, risk increases), so an agent can tell this apart from watch and verify_lock without opening a schema.

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?

Includes an explicit routing sentence: 'changes_since for up to 50 servers at once; watch for one server; verify_lock against a saved lock.' It also flags the paid-per-call precondition and points to list_paid_tools, so the agent knows both when to select this tool and what to check first.

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