Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

payment_assistant_checkout

Create a hosted Stripe Checkout session ($10, $25, $100, $250, or $500 credit pack via Card, Apple Pay, Google Pay, or Link) to fund a new or existing master X402 spend key (sbk_*) with zero crypto required.

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": "payment_assistant_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
returnNo
spend_keyNo
credit_keyNo
amount_centsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation, so the description's job is to add context beyond that. It does add useful context: the flow is a hosted third-party Stripe redirect, accepted payment methods are enumerated, and no crypto is needed. It omits what the caller receives (checkout URL/redirect), session expiry or single-use behavior, and what happens to the key on payment failure.

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?

It is a single dense sentence with the action and outcome front-loaded, and every clause carries information. The large parenthetical of dollar amounts and payment methods makes it slightly harder to parse but does not waste words.

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 mutation tool with an external payment redirect, four parameters, and no output schema, the definition covers the core flow but leaves material gaps. The return value (a checkout URL the caller must act on) and two of four parameters remain unexplained, which an agent needs before calling 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%, so the description must carry parameter meaning, and it only partially does. It maps amount_cents to the dollar tiers ($10–$500) and hints at spend_key's sbk_* format, but the `return` enum (x402/developers/app) and the `credit_key` parameter are never explained, nor is the spend_key-versus-credit_key distinction for funding new vs existing keys.

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 gives a specific verb and resource (create a hosted Stripe Checkout session) and states the outcome (fund a new or existing master X402 spend key). It does not, however, distinguish this from the sibling switchboard_card_checkout, which likely covers similar checkout territory.

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?

Usage is implied rather than stated: the tool is for funding a spend key using fiat credit packs, with 'zero crypto required' acting as a qualifying condition. There is no explicit when-not guidance, no mention of prerequisites (e.g. whether a key must exist first), and no routing to alternatives such as delegate_key or switchboard_card_checkout.

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