scdo-agent-plugins

Overview Schema Source Related Servers Discussions Admin

Create x402 wallet

create_wallet

Create or reuse an agent's x402 wallet, bind it on the Agent Ledger, and fund it with USDC on Base under configurable per-payment and daily limits; no ETH is required.

Instructions

Create or reuse the agent's x402 wallet and bind it on the Agent Ledger. Fund it with USDC on Base; no ETH is needed. maxUsdc: per-payment limit 0.001 to 1 (default 0.10). dailyUsdc: up to 20 (default 1.00).

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": {
      "bot": "<bot>"
    },
    "name": "create_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	Yes
`maxUsdc`	No
`network`	No
`dailyUsdc`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful side effects: the wallet is created or reused, bound on the Agent Ledger, and funded with USDC on Base with no ETH required. It omits permissions/auth requirements, what happens to an existing wallet's balance on reuse, and error behavior, so it stops short of a 5.

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?

Four dense clauses, each carrying distinct information (provision/bind, funding, no gas, two limit parameters with ranges and defaults). Front-loaded with the action and free of filler.

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?

No output schema and no annotations, so the description is the only source of behavior. It covers the core effects and limits but says nothing about what is returned (address, balance), what 'bot' identifies, or how reuse differs from creation — gaps an agent needs for a provisioning tool.

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 0% (titles only), so the description must compensate. It usefully documents maxUsdc (0.001–1, default 0.10) and dailyUsdc (up to 20, default 1.00), but the required 'bot' parameter is never explained and the network enum (base/base-sepolia) is only implied by 'on Base', which could mislead about the testnet option.

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 or reuse the agent's x402 wallet and bind it on the Agent Ledger'), so the agent knows this provisions a wallet rather than querying one. It distinguishes itself from read siblings like get_balance and ledger_get_agent, though it never names the nearest alternatives (register_agent, connect_start).

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?

'Create or reuse' implies idempotent usage, and the funding detail implies this is a setup step, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives. Usage is inferable rather than stated.

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