Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

switchboard_card_checkout

Create the existing hosted card checkout for a credit pack. Payment occurs only at its checkout URL.

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": {
      "amount_cents": "<amount_cents>"
    },
    "name": "switchboard_card_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
credit_keyNo
amount_centsYes

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?

The annotations already disclose that this is a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds useful behavioral context by stating that payment occurs only at the resulting checkout URL, clarifying that this call creates a checkout rather than charging directly. However, it omits important details such as whether the checkout URL is returned, expiration behavior, and any authentication requirements.

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 two short sentences and front-loads the core action. It is mostly efficient, though the phrase 'existing hosted card checkout' could be clearer and slightly more direct.

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?

With no output schema and no parameter descriptions, the description should carry more of the burden. It does not explain what the tool returns, whether the checkout URL is provided in the response, how long the checkout remains valid, or what credit_key means, leaving material gaps for an agent trying to invoke it correctly.

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%, and the description does not explain either parameter. It does not clarify that amount_cents represents a credit-pack price or currency unit, nor does it explain what credit_key is for or when it should be supplied.

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 states a specific verb and resource: creating a hosted card checkout for a credit pack. It does not explicitly distinguish this from sibling tools such as payment_assistant_checkout, and the word 'existing' is slightly ambiguous, but the core purpose is understandable.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternatives. The only implied usage context is buying a credit pack, which leaves the agent to infer when this should be selected over other checkout-related siblings.

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