Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

mobility_parking_options

Read-onlyIdempotent

Live Annapolis downtown parking options, garage rates, flood resilience tiers, shuttle/AR/guided-walk handoffs, and NOAA tidal flood detour advisory (?q=, ?water_level_ft=) 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": "mobility_parking_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
order_refNo
credit_keyNo
wallet_proofNo
wallet_addressNo
water_level_ftNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint/openWorldHint annotations, the description discloses a payment gate (HTTP 402 on unpaid calls) and the retry path via payment_signature, which is exactly the kind of behavior an agent cannot infer from annotations or schema. It stops short of describing rate limits, data freshness, or response shape, but it adds real operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, but the structure is poor: a long noun pile with query parameters wedged into parentheses mid-sentence and the critical payment-recovery note tacked on at the end. The most important operational fact (402 payment gate) should be front-loaded.

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 seven-parameter, open-world, payment-gated tool with no output schema and zero schema descriptions, the definition leaves too much unexplained: the roles of the wallet/credit/order parameters, what a successful response contains, and how the query inputs shape results. The payment retry hint is the only element that fully closes a gap.

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% across seven parameters, so the description carries the full burden, yet it only names two of them (?q= and ?water_level_ft=) and only implicitly covers payment_signature through the retry instruction. order_ref, credit_key, wallet_proof, and wallet_address are completely undocumented anywhere, leaving the agent to guess at the payment/auth flow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the subject matter (downtown parking options, garage rates, flood resilience tiers, shuttle/AR/walk handoffs, NOAA tidal flood detours) so the domain is identifiable, but it is a noun-phrase list with no verb and no statement of what the tool actually returns or does. It also does not distinguish itself from plausible siblings such as destination_annapolis_transport or destination_annapolis_reference.

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

Usage Guidelines3/5

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

The only actionable guidance is procedural: unpaid calls return HTTP 402 and should be retried with payment_signature, which tells the agent how to recover from a failed call. There is no statement of when to choose this tool over alternatives, no prerequisites, and no indication of whether q and water_level_ft are meant to be combined.

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