Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

destination_annapolis_reference

Read-onlyIdempotent

Authoritative Annapolis destination reference snapshot — curated businesses, portals, transport, access points, places, and official events calendar (?q=) Unpaid calls return HTTP 402 requirements; retry with payment_signature.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "destination_annapolis_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
order_refNo
credit_keyNo
wallet_proofNo
wallet_addressNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds useful non-obvious context that unpaid calls return HTTP 402 and can be retried with payment_signature, but it does not explain payment flow, cost, or how the other payment and identity parameters affect access.

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 a single front-loaded sentence with no wasted framing, moving from resource identity to content categories to payment behavior. It is dense but readable, with only minor awkwardness in the phrase 'HTTP 402 requirements'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

For a six-parameter paid reference tool with no output schema and zero parameter descriptions, the definition leaves most invocation details opaque. It lists the content categories and one retry behavior, but an agent lacks enough information about payment and identity parameters to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for six parameters. The description only hints at q via '(?q=)' and explains payment_signature as a retry credential; order_ref, credit_key, wallet_proof, and wallet_address are left unexplained, so the description does not compensate for the schema gap.

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 specific resource, the Annapolis destination reference snapshot, and enumerates its content categories: businesses, portals, transport, access points, places, and events calendar. This is clear enough to distinguish it from generic catalog tools, though it does not explicitly separate it from the sibling transport-specific tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no when-to-use or when-not-to-use guidance and names no alternatives. The only operational hints are the ?q= query marker and the payment-retry instruction, neither of which tells an agent when this tool is the right choice.

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