Skip to main content
Glama

Quantum Atlas Stripe X402 Agent Payment Hub

List X402 Capabilities

x402_list_capabilities
Read-onlyIdempotent

List all priced HTTP 402 capabilities, exact USD rates, per-capability JSON input_schema, example_arguments, capability lanes, free discovery tools, and Stripe spend-key payment rules. Use this first to discover valid capability_id values and exact argument schemas before calling x402_quote_plan or x402_execute_capability (pass capability_id to inspect a single capability cleanly). Do not use this to verify live ledger availability (use x402_check_health) or compute multi-item totals (use x402_quote_plan). Requires no authentication, incurs no charge, and never mutates state.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402_list_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
laneNoOptional capability lane filter: live_data (maritime/harbor/parking oracles), studio_audio (GPU stem separation), switchboard (11-language voice/broadcast), member_tools (KB/co-creation), or live_broadcast.
capability_idNoOptional specific capability_id or route key to inspect (e.g. "reality_harbor_state", "audio_visual_isolate", or "POST /switchboard/chunk") when retrieving its exact input_schema and example_arguments without loading all 25 capabilities.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the capability catalog loaded successfully.
lanesNoGrouped capability lanes with pricing cards.
schemaNoContract schema identifier (atlas.x402.capability_payment_center.v1).
capabilitiesNoFlat list of priced HTTP 402 capabilities including exact input_schema and example_arguments.
zero_crypto_requiredNoTrue indicating Stripe USD prepaid settlement with zero crypto wallet required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / capability_id
      Added value: +{
      +  "description": "Optional specific capability_id or route key to inspect (e.g. \"reality_harbor_state\", \"audio_visual_isolate\", or \"POST /switchboard/chunk\") when retrieving its exact input_schema and example_arguments without loading all 25 capabilities.",
      +  "maxLength": 160,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / properties / capabilities / description
      Previous value: -"Flat list of priced HTTP 402 capabilities."New value: +"Flat list of priced HTTP 402 capabilities including exact input_schema and example_arguments."
    • addedOutput schema / properties / capabilities / items / properties / example_arguments
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / capabilities / items / properties / input_schema
      Added value: +{
      +  "additionalProperties": {},
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the 'never mutates state' clause is largely redundant. However, the description adds genuinely new context: no authentication required, no charge incurred, and the hint that a full listing spans ~25 capabilities, which motivates the single-capability inspection mode.

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?

Three sentences, front-loaded with purpose, then usage ordering, then exclusions and safety. The opening sentence is a long comma-separated inventory that is dense but each item is a real deliverable of the call, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value detail is unnecessary, and the description covers the remaining decisions an agent must make: when to call first, what it returns at a glance, cost/auth posture, and which siblings to use instead. Nothing needed for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds semantic framing beyond the schema: capability_id is positioned as an inspection mode that retrieves one capability's input_schema and examples 'without loading all 25 capabilities', and the tool is framed as the discovery step for valid capability_id values. Lane filtering is left entirely to the schema, which documents it well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb ('List') and resource ('priced HTTP 402 capabilities') and then enumerates the payload contents: USD rates, per-capability input_schema, example_arguments, lanes, free discovery tools, and payment rules. It is clearly distinguishable from sibling tools such as x402_check_health and x402_quote_plan, which are named later.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Use this first to discover valid capability_id values and exact argument schemas before calling x402_quote_plan or x402_execute_capability', giving both ordering and downstream purpose. It also names two negative cases with the correct alternatives (x402_check_health for live ledger availability, x402_quote_plan for multi-item totals).

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