Moneda

add_wallet

Add a crypto wallet to the user's saved external accounts. IMPORTANT: The wallet must support USDC, EURC, CHFAU, CADD, and MXNB on the Base network. Sending other tokens or using other chains will result in permanent loss of funds. The user MUST confirm they understand this before the wallet is saved — set confirmed=true only after explicit user acknowledgment.

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": {
      "walletName": "<walletName>",
      "walletAddress": "<walletAddress>",
      "confirmed": "<confirmed>"
    },
    "name": "add_wallet"
  }
}

Input Schema

Name	Required	Description
`confirmed`	Yes	Set to true ONLY after the user has explicitly confirmed the wallet supports USDC/EURC/CHFAU/CADD/MXNB on Base. If false, the tool returns a confirmation prompt instead of saving.
`walletName`	Yes	A descriptive name for the wallet (e.g. 'My Coinbase Wallet')
`walletAddress`	Yes	The wallet address (0x-prefixed hex, 42 characters)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say it's non-read-only and non-destructive; the description goes much further by disclosing the irreversible loss-of-funds risk, the supported asset/network whitelist, and the key behavioral fact that confirmed=false returns a prompt instead of saving. That is exactly the context annotations can't convey.

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?

Three sentences, front-loaded with purpose, then the hard constraint, then the confirmation protocol. No filler; each sentence carries a distinct obligation.

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

Completeness5/5

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

No output schema exists, and the description covers the one return path that matters (a confirmation prompt when confirmed=false), the risk model, and the required inputs. Nothing an agent needs to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented; the description nonetheless reinforces the semantics of confirmed as a gated acknowledgment rather than a plain boolean, adding interaction meaning beyond the schema wording.

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 first sentence gives a specific verb and resource ('Add a crypto wallet to the user's saved external accounts'), which cleanly separates it from sibling adders like add_bank and add_contact_external. An agent can identify the tool's function without opening the schema.

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?

The description gives a clear precondition sequence: verify token/chain support, obtain explicit user acknowledgment, then set confirmed=true. It doesn't explicitly contrast with add_bank or other account-adding siblings, so the alternative routing is left implicit.

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

All Moneda 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?