Skip to main content
Glama
aibtc-mcp-server
by aibtcdev

wallet_unlock

Unlocks the agent's wallet to enable transactions, using the active wallet unless a wallet ID is specified; omit the password when the server has it configured.

Instructions

Unlock the agent's wallet to enable transactions. If no wallet ID is provided, unlocks the active wallet. Omit password when the server has AIBTC_WALLET_PASSWORD_FILE or AIBTC_WALLET_PASSWORD set: the server reads it, so it never enters the conversation. The configured password only unlocks the wallet that was active when the server started, and that unlock keeps the current session's spend budget.

Tip: call earning_opportunities to see how to put your assets to work.

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_unlock"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordNoWallet password - WARNING: sensitive value. Omit it to use AIBTC_WALLET_PASSWORD_FILE / AIBTC_WALLET_PASSWORD from the server's environment.
walletIdNoWallet ID to unlock (uses active wallet if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.77.3
    • changedInput schema / properties / password / description
      Previous value: -"Wallet password - WARNING: sensitive value"New value: +"Wallet password - WARNING: sensitive value. Omit it to use AIBTC_WALLET_PASSWORD_FILE / AIBTC_WALLET_PASSWORD from the server's environment."
    • removedInput schema / required
      Removed value: -[
      -  "password"
      -]
  2. First observedv1.77.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavioral traits: the env-var path keeps the secret out of the conversation, and the unlock retains the current session's spend budget. It is silent on failure modes (wrong password, locked/absent wallet) and on whether unlocking is idempotent, which keeps it below a 5.

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?

The core behavior and the safety-critical password guidance are front-loaded in the first three sentences, with no redundant restatement. The trailing 'earning_opportunities' tip is a soft upsell that is only loosely tied to unlocking, so it slightly dilutes an otherwise tight definition.

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 two-parameter, zero-required tool with no output schema, this covers purpose, defaulting, secret handling, and the configured-password limitation well. What's missing is error behavior and confirmation of what a successful unlock returns, but neither is essential 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 both parameters are already documented with sensible descriptions. The description reinforces the password-omission semantics and the active-wallet default, adding rationale but no new syntax or format detail beyond the schema. 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 opens with a specific verb and resource ('Unlock the agent's wallet to enable transactions'), which tells an agent exactly what state change results. It doesn't explicitly distinguish itself from the unlock-flavored siblings (credentials_unlock, lightning_unlock, pillar_key_unlock), so it falls short of a 5.

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 gives concrete conditional guidance: omit the password when AIBTC_WALLET_PASSWORD_FILE or AIBTC_WALLET_PASSWORD is set, and the wallet ID defaults to the active wallet. It also warns that a configured password only unlocks the wallet active at server start. It never states when to prefer a sibling unlock tool, so no exclusions are covered.

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