Skip to main content
Glama
Sign In
Wallet MCP Server

Wallet MCP Server

by askjimmy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wallet_delete

Permanently remove a stored wallet by wallet ID, using the keystore password to confirm ownership before deletion.

Instructions

Delete a stored wallet (requires password to confirm ownership).

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": {
      "walletId": "<walletId>",
      "password": "<password>"
    },
    "name": "wallet_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYesKeystore password to verify ownership
walletIdYesWallet ID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose that a password is required to verify ownership, which is a real behavioral trait. However, for a destructive wallet operation it omits whether deletion is irreversible, what happens to funds/keys, and any confirmation behavior — gaps a delete tool should address.

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?

A single front-loaded sentence with the destructive action first and the auth requirement immediately after; no wasted text.

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?

For a destructive, two-parameter tool with no annotations and no output schema, the description covers the auth requirement but says nothing about irreversibility or consequences. It is minimally adequate but not complete for a delete operation.

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 both parameters are already documented ("Keystore password to verify ownership", "Wallet ID (UUID)"). The description's note about password ownership verification largely restates the schema, so it adds little beyond the baseline.

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 ("Delete a stored wallet"), which is unambiguous and easily separated from the sign/list/generate siblings. It does not explicitly name or contrast with any sibling, but the operation itself is clear.

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 parenthetical gives a prerequisite (password needed to confirm ownership) but offers no when-to-use vs. when-not guidance or alternatives among the wallet_* family. Usage is only implied by the verb.

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