Skip to main content
Glama
Sign In
x402-wallet-mcp

x402-wallet-mcp

by kato9292929
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Show wallet (funding info)

show_wallet_app
Read-only

Displays wallet funding details and current spending limits for a chain or all chains, so users can see deposit addresses, faucet/onramp links, and approved budgets.

Instructions

Text replacement for the wallet UI: deposit address and chain for funding, faucet/onramp links, and the current spending limits. Limits can only be changed by the wallet owner in the config file.

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": "show_wallet_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoCAIP-2 chain id, e.g. "eip155:84532" (Base Sepolia) or "eip155:8453" (Base). Omit for all chains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds genuinely useful non-schema context: that limits are immutable from this tool and only the wallet owner can change them via the config file, which prevents a futile write attempt. It also discloses the output's framing as a text rendering of the wallet UI.

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, content-first, with no filler; the constraint on changing limits is placed last where it reads as a caveat. Minor jargon ('Text replacement for the wallet UI') costs a little immediate clarity.

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?

With no output schema, the description correctly carries the burden of describing return content, and it enumerates the components well. A short note on whether the data is per-chain scoped when 'chain' is omitted would close the remaining gap.

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%, and the single 'chain' parameter is documented with CAIP-2 examples and the 'omit for all chains' default. The description's mention of 'chain for funding' adds no meaning beyond the schema, so the baseline 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 names the resource and enumerates the returned content (deposit address, chain, faucet/onramp links, spending limits), which is far more than the name 'show_wallet_app' conveys. It is weakened by unaddressed overlap with siblings get_wallet_address and get_wallet_balance, so the agent cannot immediately tell which to call for an address alone.

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?

'Text replacement for the wallet UI' implies a presentational, funding-oriented use case, which is a reasonable implicit cue. However, it never states when to pick this over get_wallet_address or get_wallet_balance, nor any exclusions, leaving the sibling overlap to inference.

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