Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_quote

Read-onlyIdempotent

Quote the exact existing API order before paying; no speech is generated.

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": {
      "route": "<route>",
      "order": "<order>"
    },
    "name": "switchboard_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes
routeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already carry readOnly, idempotent and non-destructive, so safety is covered. The description's one addition, "no speech is generated," is meaningful context because the switchboard family includes speech/media products, but it does not say what the quote returns or whether the quote expires.

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?

A single short sentence, front-loaded with the verb and with no filler. It is terse to the point of being cryptic, but nothing is redundant.

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 two-parameter tool with an untyped nested object, no output schema and no documented return value, the description does far too little. It never establishes what a call yields (price? availability?) or how the opaque `order` payload should be shaped, which is exactly what an agent needs before invoking 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 coverage is 0% and the required `order` parameter is a free-form nested object, so the schema explains nothing. The description says only that the order must be an "exact existing" one, never indicating required keys or how `route`'s seven enum values relate to the order payload.

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?

"Quote" is a specific verb and the target is an existing order, so the general intent (get a price before paying) is discernible. But "the exact existing API order" is jargon that never defines what an order object is, and no sibling quote tool (bazaar_quote, payment_assistant_quote) is distinguished.

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?

"before paying" gives an implied usage moment — call it after building an order and prior to payment — which is real guidance. There are no explicit exclusions and no named alternative for the other quote tools, so the agent must infer which quote endpoint applies to which flow.

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