Skip to main content
Glama
Sign In
Wallet MCP Server

Wallet MCP Server

by askjimmy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wallet_list

Lists all stored wallets with addresses and metadata only, never private keys. Filter results by chain ID to find wallets for a specific network.

Instructions

List all stored wallets (addresses and metadata only, no private keys).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wallet_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional: filter by chain ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that output is limited to addresses and metadata and never private keys, which is real behavioral value. It says nothing about pagination, ordering, authentication requirements, or whether the operation is strictly read-only.

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?

One sentence, front-loaded with the action and resource, with the key safety-relevant qualifier attached. No wasted words.

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

Completeness4/5

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

For a zero-required-parameter list tool with no output schema, the description covers the essentials: what is returned and what is deliberately excluded. Only minor gaps remain (ordering, pagination, auth), so an agent has enough to call 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 coverage is 100%, so the single 'chain' filter is already documented in the schema. The description adds no further detail about the filter's accepted values or behavior, so the baseline of 3 applies.

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 gives a specific verb and resource ('List all stored wallets') and adds a scope qualifier ('addresses and metadata only, no private keys') that separates it from siblings like wallet_export or wallet_sign_*. It stops short of naming the alternative tools, but the resource 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?

Usage is only implied by the verb 'List' — there is no explicit statement of when to call this versus wallet_get_balance, wallet_export, or wallet_get_public_key. The 'no private keys' note hints at what this tool is not for, but no alternative is named.

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

Deploy Server

Other Tools