@txn-dev/mcp-server

create_wallet

Create a new agent wallet for sending and receiving payments. Specify a display name and optional currency to enable your AI assistant's transactions.

Instructions

Create a new agent wallet for sending and receiving payments

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Display name for the wallet (e.g. 'translation-agent')
`currency`	No	Wallet currency. Defaults to usd

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Oct 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention whether the wallet is created on-chain, if it requires authentication, whether it incurs a cost, or what happens on success (e.g., returns wallet ID). For a creation tool with zero annotation coverage, this is a significant gap.

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?

The description is a single concise sentence that front-loads the core action. There is no wasted language.

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?

Given this is a creation tool with no annotations, no output schema, and no behavioral details in the description, the definition is incomplete. It omits critical context such as authentication needs, side effects, return values, and prerequisites, which an agent would need to invoke it correctly.

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 100%, so the schema already documents both parameters (name and currency) with clear descriptions and defaults. The tool description adds no additional parameter meaning beyond what the schema provides, so baseline 3 is appropriate.

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?

Clear verb+resource combination ('Create a new agent wallet') that distinguishes it from siblings like list_wallets or fund_wallet. The added phrase 'for sending and receiving payments' clarifies the purpose of the resource. No explicit sibling naming, but the action is unambiguous.

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 description implies usage by stating the wallet is for sending and receiving payments, which suggests it is a setup step before those actions. However, it doesn't explicitly state when to use this tool versus alternatives or mention any prerequisite conditions (e.g., 'use before pay or fund_wallet').

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

Deploy Server