Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

reality_situation

Read-onlyIdempotent

Fused multi-domain situation snapshot for one 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_situation"
  }
}

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

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description's real contribution is the gating behavior: unpaid calls return HTTP 402 with requirements and must be retried with payment_signature. That is genuinely useful, but return shape, caching/freshness of the "snapshot", and whether payment is per-call or per-session remain undisclosed.

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 compact sentences with the purpose front-loaded and the payment caveat second, which is the right ordering. The embedded "(?destination=)" query-string fragment is slightly noisy but not harmful.

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?

For a read-only snapshot tool with no output schema, the description covers the payment path adequately, but six parameters at 0% schema coverage means an agent cannot construct a valid paid call from the definition alone. It stops short of describing what a "fused multi-domain" payload contains, which is the tool's whole value.

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 carries the full burden and only explains two of them (destination and payment_signature). The roles of order_ref, credit_key, wallet_proof and wallet_address, and how payment_signature relates to wallet_proof, are left entirely undocumented.

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?

"Fused multi-domain situation snapshot for one destination" gives a resource and a scope (a single destination), but "situation snapshot" is abstract and never says what domains are fused or what the caller actually gets back. It does not differentiate itself from the many reality_* and destination_* siblings that also deal with destinations.

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 only procedural guidance is the payment retry loop (HTTP 402, then retry with payment_signature). There is no statement of when to choose this fused snapshot over the narrower siblings like reality_marine_state or reality_harbor_state, and no prerequisites are spelled out beyond the payment note.

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