DevX Agent Hub

Crypto payment request + QR code

create_crypto_payment_request

Read-onlyIdempotent

Create a wallet-scannable crypto payment request: EIP-681 URI (USDC or ETH on Base/Polygon/Arbitrum/Optimism/Ethereum), BIP21 (Bitcoin) or Solana Pay link plus a QR code SVG, after validating the recipient. For invoices and checkouts. $0.01 USDC on Base via x402. Price: $0.01. First call returns the x402 PaymentRequired (no charge); retry with payment in _meta["x402/payment"].

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": {
      "to": "<to>",
      "amount": "<amount>"
    },
    "name": "create_crypto_payment_request"
  }
}

Input Schema

Name	Required	Description
`to`	Yes
`chain`	No
`label`	No
`token`	No
`amount`	Yes
`message`	No
`x402_payment`	No	Optional. Base64 x402 v2 PaymentPayload, for clients that cannot set params._meta["x402/payment"]. Omit on the first call to get the exact price.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds important behavior beyond the annotations: it explains the x402 payment flow, the exact price, that the first call returns PaymentRequired without charging, and how to retry with payment. These are critical operational details an agent would not infer from readOnly/openWorld/idempotent/destructive annotations.

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 front-loaded with the core action and output, then follows with usage and payment details. It is dense but appropriate for the tool's complexity, with minor redundancy in repeating the $0.01 price.

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

Completeness4/5

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

Given the complexity of crypto payment protocols and the lack of an output schema, the description covers the main outputs, supported chains/tokens, validation step, and payment flow. It is mostly complete, though it leaves parameter formatting and error behavior under-specified.

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 description coverage is only 14%, so the description must compensate. It clarifies the token/chain/protocol mapping for EIP-681, BIP21, and Solana Pay, but it does not explain the format of required parameters like `to` and `amount`, nor the meaning of `label` or `message`.

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?

States a specific verb and resource: create a crypto payment request that returns an EIP-681/BIP21/Solana Pay link plus QR code SVG. The purpose is clear and distinct from siblings like verify_crypto_payment, but the description does not explicitly differentiate itself from those sibling tools.

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

Usage Guidelines4/5

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

Gives clear usage context: "For invoices and checkouts" and notes recipient validation before request creation. It does not state when not to use it or explicitly name alternative tools, so it stops short of full routing guidance.

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

All DevX Agent Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?