Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

destination_ocean_city_reference

Read-onlyIdempotent

Authoritative Ocean City, MD 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_ocean_city_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

B3.1/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, open-world operation. The description adds material behavioral detail beyond annotations: unpaid calls return HTTP 402 and should be retried with payment_signature, which is important for correct invocation. It does not disclose response format or pagination, but the payment behavior is a meaningful addition.

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 compact and front-loads the destination reference scope before the payment caveat. The em-dash list and parenthetical make it slightly cramped, but every clause contributes useful information.

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 tool with six undocumented parameters, no output schema, and a paid-access flow, the description is incomplete. It explains the payment retry path and query parameter at a high level but leaves the roles of four parameters and the shape of the returned snapshot unclear.

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 six parameters, so the description must carry the burden. It explains only q (as a query) and payment_signature (as the retry mechanism after HTTP 402), leaving order_ref, credit_key, wallet_proof, and wallet_address undocumented in both schema and description.

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?

The description identifies a specific resource and geographic scope: an authoritative Ocean City, MD destination reference snapshot covering businesses, portals, transport, access points, places, and events. It distinguishes itself from the Annapolis sibling by city and content scope, though it lacks an explicit verb such as 'retrieve'.

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?

The description gives no when-to-use guidance, no exclusions, and no comparison to alternatives. It mentions the ?q= query and payment retry flow, but those are invocation details rather than guidance on selecting this tool.

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