Skip to main content
Glama

prepare_x402_donation

Read-onlyIdempotent

Prepare an optional Base USDC x402 donation directly to Wallet EB. No transfer occurs here. Your x402 wallet signs and sends the HTTP payment within your operator-authorized budget. Existing report services remain free.

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_usd": "<amount_usd>"
    },
    "name": "prepare_x402_donation"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description is consistent with them by stating no transfer occurs here. It adds real context beyond the annotations — the caller's x402 wallet signs and sends the HTTP payment within an operator-authorized budget — but leaves open what the tool actually returns and what happens if the budget is exceeded.

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?

Four short sentences, front-loaded with the resource and immediately followed by the key caveat that no transfer happens here. No filler, though the budget/wallet sentence could be tightened slightly.

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 simple one-parameter preparation tool with annotations covering the safety profile, the description covers intent, recipient and the no-transfer behavior. It is incomplete on the two things an agent still needs: the amount format and what the prepared payment artifact looks like, since no output schema exists to explain the return value.

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 coverage is 0% for the single parameter, so the schema provides no documentation of amount_usd at all beyond its name and string type. The description never mentions the amount, its expected format (decimal string? integer cents?), minimum, or currency assumption, so it fails to compensate for the coverage gap.

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 (prepare) plus a specific resource (Base USDC x402 donation to Wallet EB) and immediately clarifies that no transfer occurs. The x402/Base-USDC framing differentiates it from generic siblings like prepare_donation or prepare_payment, though it never names an alternative directly.

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 word 'optional' and 'Existing report services remain free' imply this is an opt-in add-on rather than a required step, which is useful context. However, it does not say when an agent should choose this over prepare_donation or prepare_payment, nor what precondition (e.g. a completed report) must hold.

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