Skip to main content
Glama

X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router

create_checkout

Idempotent

Create a UCP checkout session for API passes or credits. Example: create_checkout(line_items=['agd-pass-2000'])

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

Input Schema

NameRequiredDescriptionDefault
buyerNoOptional buyer contact details.
line_itemsNoLine items for checkout.

Output Schema

NameRequiredDescriptionDefault
storeYesMerchant domain identifier.
ucp_versionNoSupported UCP specification version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare the tool is non-read-only, non-destructive, idempotent, and closed-world. The description adds the target domain and an example but does not disclose additional behavioral context such as permissions, side effects, or idempotency semantics beyond what annotations provide.

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?

The description is two sentences, front-loads the core action, and includes a compact example with no wasted text.

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?

The description is sufficient for a simple create operation alongside a rich schema and output schema, but given the many sibling cart/checkout tools and nested buyer parameter, it lacks explicit differentiation and does not mention buyer handling.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents both parameters. The example shows one line_items value format, but the description does not mention the optional buyer object or further clarify line item structure.

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: "Create a UCP checkout session," and narrows the scope to "API passes or credits" with an example. It distinguishes checkout from cart in general, but does not explicitly explain when to use it instead of siblings like create_cart or complete_checkout.

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 description gives an implied use case (API passes or credits) and a concrete example invocation, which helps an agent understand intended usage. However, it does not state when not to use this tool or name alternatives among the many cart/checkout 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.