Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_card_order_get

Read-onlyIdempotent

Recover one exact credit purchase by stable order_ref.

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": {
      "credit_key": "<credit_key>",
      "order_ref": "<order_ref>"
    },
    "name": "switchboard_card_order_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_refYes
credit_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds the useful nuance that matching is exact and keyed on a stable identifier (no fuzzy or partial lookup), but says nothing about permissions, not-found behavior, or rate limits.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the lookup key and the exactness constraint are stated immediately.

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 single-record lookup with full annotations and no output schema, the essentials are present. However, the undocumented credit_key and the absence of any statement about what a recovered purchase contains or what happens when the ref is unknown leave real gaps.

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 two required parameters, so the description must carry the load. It gives meaning to order_ref ('stable', 'exact') but never mentions credit_key, leaving one of two required parameters entirely undefined in both schema and prose.

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 verb and resource ('Recover one exact credit purchase') and a lookup key ('by stable order_ref'), which distinguishes it from the plural list-style sibling switchboard_card_orders. It stops short of naming any sibling explicitly, so an agent must infer the boundary.

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 phrase 'by stable order_ref' implies the precondition for use: you must already hold the exact order reference. There is no explicit when-not guidance and no named alternative for listing or fuzzy-searching orders, so the routing signal is only implied.

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