Skip to main content
Glama

Deposit USDC (x402)

create_x402_deposit

Agent-native funding: returns x402 v2 payment requirements (USDC on Base). Sign with an x402 client and re-call with the X-Payment header via the REST endpoint.

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_cents": "<amount_cents>"
    },
    "name": "create_x402_deposit"
  }
}

Input Schema

NameRequiredDescriptionDefault
amount_centsYes
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a non-readonly, open-world, non-idempotent, non-destructive operation. The description adds genuinely new behavioral information: this call does not move funds, it returns payment requirements, and completion happens elsewhere with an X-Payment header. It does not say whether requirements expire, what happens on a failed or duplicate payment attempt, or what amount_cents maps to in USDC terms.

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?

Two sentences, front-loaded with the funding purpose and followed by the required follow-up action. 'Agent-native funding' is mildly promotional jargon, but nothing is redundant enough to cut.

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?

This is a multi-step payment flow with no output schema and no parameter documentation, so the description needs to work harder. It explains the hand-off to the REST endpoint but leaves the shape of the returned payment requirements, expiration handling, and error behavior unspecified.

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 description coverage is 0%, so the description carries the full burden and does not deliver. Neither amount_cents (units, minimum 100, relationship to USDC's six-decimal denomination) nor workspace_id is explained anywhere, leaving the agent to guess at the most consequential input.

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 makes the resource and mechanism clear: it returns x402 v2 payment requirements for funding a deposit in USDC on Base. What it omits is the verb-level distinction from the closest sibling, create_wallet_deposit, so an agent cannot tell from this text which funding path to choose.

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?

'Agent-native funding' plus the instruction to sign with an x402 client and re-call with the X-Payment header implies the intended context and the follow-up step. There is no explicit when-to-use versus when-not, and no mention of prerequisites such as requiring an x402-capable client or a funded wallet.

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.