Skip to main content
Glama

Compact tool cards for an MCP server (7Maps)

tool_card
Read-onlyIdempotent

Use this instead of loading a server's full tool definitions when you only need to choose a tool or prepare a call: one compact card per tool (what it does, its arguments with required ones marked *, risk level and side effects) plus a hash of the full definition. Usually 70 to 90% fewer tokens than the server's own tool list. Optionally only the named tools. For a server that asks for sign-in before listing its tools: that it is up and how to connect (no charge). 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>"
    },
    "name": "tool_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolsNoOnly these tools; all when omitted
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.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds useful context beyond them. It discloses the card contents, the included definition hash, the typical 70-90% token reduction, that sign-in probing is free, and that actual server access is paid per server. It also explicitly says the tool reads the map only, which reinforces the safety profile.

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 description is dense but front-loaded: the primary use case appears first, followed by token savings, optional filtering, sign-in behavior, and pricing. Every sentence carries relevant information, though the semicolon-heavy packing makes it slightly harder to scan than a cleaner bulleted or shorter phrasing would be.

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 read-only card-generation tool with no output schema, the description explains what each card contains, what metadata is included, how optional filtering works, and how sign-in and payment are handled. An agent has enough information to decide when to call it and what to expect from the result.

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 100%, so the schema already documents the four parameters in detail. The description still adds meaning by explaining that tools can optionally restrict the output to named tools, that server may be a URL or registry name in the sign-in case, and that payment/licensing is handled per server. This is useful beyond the schema, though most parameter detail remains schema-driven.

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?

The description states a specific function: returning compact per-tool cards for an MCP server instead of loading full tool definitions. It distinguishes the tool from siblings by framing it as a token-saving alternative to the server's own tool list and by pointing to list_paid_tools for pricing details. An agent can identify the resource and intended output without opening the 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?

It gives an explicit condition for use: when you only need to choose a tool or prepare a call, use this instead of loading full definitions. It also covers the optional subset case and the sign-in-before-listing case, while noting that pricing is paid per server and referring to list_paid_tools. The when-to-use guidance is unusually direct.

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