vibe-hardware-mcp

calligraphy_create_coinbase_checkout

Creates a 1-Click Coinbase Pay/Onchain Payment checkout session and x402 AI-agent payment URL for a job, settling in USDC on Base via token conversion and gas-dust sweeping.

Instructions

Create a 1-Click Coinbase Pay / Coinbase Onchain Payment Protocol checkout session (and x402 AI-agent payment URL) settling in USDC on Base (chain_id=8453) with automatic DEX token conversion and zero gas-dust sweeping.

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": {
      "job_id": "<job_id>"
    },
    "name": "calligraphy_create_coinbase_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job ID returned by calligraphy_compile_board.
`network`	No		base
`currency`	No		USDC

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose important traits such as USDC/Base settlement, automatic DEX token conversion, and zero gas-dust sweeping. However, it omits permissions, idempotency, whether checkout creation has side effects beyond returning a URL, and failure behavior, so it is only minimally adequate.

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 sentence, front-loaded with 'Create' and containing no filler; each clause adds a concrete capability or settlement detail. It is dense with protocol jargon, but not verbose.

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 payment-creation tool with no annotations, no output schema, and incomplete parameter descriptions, the definition leaves too much unspecified. It says what is created and how settlement works, but not what the call returns, auth/rate-limit requirements, or failure cases.

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 only 33%: job_id is described, but network and currency are not. The description supplies settlement meaning ('USDC on Base', 'chain_id=8453') that helps interpret those two optional parameters, but it does not explain whether they can be overridden or what other values are valid, and it never explicitly mentions job_id.

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?

The description uses a specific verb, 'Create,' and names the exact resource: a Coinbase Pay / Onchain Payment Protocol checkout session plus an x402 payment URL. It also states settlement asset/chain and conversion behavior, making the tool clearly distinguishable from sibling payment-verification or job-status tools.

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?

It implies the tool is used when a checkout or payment URL is needed, but gives no explicit when-to-use conditions, prerequisites, or alternatives to calligraphy_verify_stablecoin_payment. The job_id prerequisite appears only in the schema, not in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server