Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

reality_perception_corridors

Read-onlyIdempotent

Live derived camera corridor activity, aggregate crowd and vessel counts, water state, and freshness for one tracked destination (?destination=) Unpaid calls return HTTP 402 requirements; retry with payment_signature.

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": {
      "destination": "<destination>"
    },
    "name": "reality_perception_corridors"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_refNo
credit_keyNo
destinationYes
wallet_proofNo
wallet_addressNo
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior, so the safety profile needs no restating. The description adds genuinely useful behavior the annotations cannot convey: the endpoint is pay-gated, returns HTTP 402 with requirements when unpaid, and requires a payment_signature retry. It also flags that values are 'derived' and include a freshness indicator, which tells the agent results may be approximate and time-stamped. Return format and rate limits remain unstated.

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?

Two sentences, front-loaded with what the tool returns and followed by the failure/retry rule; nothing is padding. The first sentence is an unpunctuated run-on and the inline '(?destination=)' is a bit cramped, but the information density is good and the ordering is correct.

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

Completeness3/5

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

The single largest gotcha for this tool — the 402 payment flow — is documented, which prevents the most likely invocation failure. But with 0% schema coverage, 6 parameters, and no output schema, the description leaves half the credential parameters and the shape of the returned data unexplained, so an agent still cannot fully assemble a successful call from it.

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 6 parameters, so the description carries the full burden. It only clarifies destination (as a query-string parameter) and payment_signature (as the retry credential). Four parameters — order_ref, credit_key, wallet_proof, and wallet_address — are left entirely unexplained, which is a serious gap for a pay-gated tool where those credentials determine whether the call succeeds.

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 names a concrete resource and output set: live derived camera corridor activity, aggregate crowd and vessel counts, water state, and freshness for one tracked destination. That is far more specific than the title alone and distinguishes it from pure state/tide siblings like reality_marine_state. It stops short of explicitly naming which sibling to use instead, so it lands at 4 rather than 5.

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?

There is explicit operational guidance for the payment failure path: unpaid calls return HTTP 402 and the caller should retry with payment_signature. However, there is no guidance on when to choose this tool over the many reality_* siblings (harbor state, marine vessels, situation), so selection context is only implied by the output description.

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