Skip to main content
Glama

select_wallet

Idempotent

Switch the active wallet at runtime in Encrypted Storage mode; use list_wallets to find available wallet IDs before changing.

Instructions

Switch the active wallet at runtime. Use list_wallets to see available wallet IDs. Only available in Encrypted Storage mode.

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

Input Schema

NameRequiredDescriptionDefault
walletIdYesThe wallet ID to switch to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare non-read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds real context the annotations lack: this mutates session state at runtime and is gated to Encrypted Storage mode. It does not say whether the previously active wallet is deactivated, whether in-flight operations are affected, or what errors occur for unknown/foreign wallet IDs.

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 short sentences: action first, then how to get the required input, then the availability constraint. Every sentence carries information and nothing is redundant.

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 one-parameter, no-output-schema state switch, the definition covers what it does, how to obtain the ID, and the mode restriction. The remaining gap is post-switch behavior and error cases, which is minor at this complexity level.

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?

Single parameter with 100% schema description coverage, so the schema already explains walletId. The description only redirects to list_wallets for valid values, adding a discovery hint but no format or validation semantics beyond the schema.

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?

"Switch the active wallet at runtime" gives a specific verb (switch) and resource (active wallet) plus the state-changing scope (runtime), which is more informative than the title alone. It does not differentiate from sibling wallet tools like get_wallet_address beyond naming list_wallets as the ID source.

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?

It names the concrete prerequisite step (call list_wallets to obtain a wallet ID) and states an availability gate (Encrypted Storage mode only). It stops short of stating when-not to use it or what to expect if the switch fails.

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