Skip to main content
Glama

Verify a pinned tool list (7Maps)

verify_lock
Read-onlyIdempotent

Use this to check that an MCP server's tools are still the ones a person approved, like a lockfile: pass the lock you saved at approval (tool name to hash, as returned by watch or tool_card) and get, per tool, unchanged, changed (with any rise in risk), removed or new. Catches rug pulls, where a tool changes after approval, which MCP clients do not re-ask about. Which to use: verify_lock against your saved lock; watch for one server since a date; changes_since for many servers. Paid per server (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": {
      "server": "<server>",
      "lock": "<lock>"
    },
    "name": "verify_lock"
  }
}

Input Schema

NameRequiredDescriptionDefault
lockYesTool name to hash, saved at approval
serverYesThe server URL or its official registry name
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and openWorldHint false, so the description's added value is the commercial and operational context: "Paid per server (see list_paid_tools)" and "Reads the map only," which bounds the cost and the side-effect surface. It also discloses the return shape and the "rise in risk" signal for changed tools, though it says nothing about what happens when the server cannot be resolved or the lock is malformed.

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-loaded with the purpose, then the input, then the return shape, then the sibling routing — a sensible order with no filler sentences. It is dense to the point of cramming parentheticals ("with any rise in risk", "see list_paid_tools"), but 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with nested objects and no output schema, the description still supplies the return semantics (per-tool unchanged/changed/removed/new), the cost model, and the safety statement. Nothing required to decide whether and how to call it is missing; the untold remainder (last_trip fields) is fully documented in the schema.

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 coverage is already 100%, so the baseline is 3; the description goes beyond it by explaining the provenance of "lock" — "tool name to hash, as returned by watch or tool_card" — which tells the agent where to obtain a valid value and how it must be shaped. The last_trip and license_key parameters are left entirely to the schema, so this is not exhaustive.

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?

"Check that an MCP server's tools are still the ones a person approved, like a lockfile" names a specific verb (check/verify) and a specific resource (a pinned tool list), plus the output axis: unchanged, changed, removed or new per tool. The rug-pull framing tells an agent exactly which problem class this addresses and separates it from watch and changes_since.

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?

Explicit routing sentence: "verify_lock against your saved lock; watch for one server since a date; changes_since for many servers." Each alternative is named with the condition that selects it, and the required precondition (you must already hold a lock saved at approval) is stated up front.

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