AgentWallet MCP Server

pause_wallet

Pause a specified wallet to block transaction signing during an emergency until it is resumed.

Instructions

Emergency pause a wallet. No transactions can be signed while paused.

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": {
      "wallet_id": "<wallet_id>"
    },
    "name": "pause_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`wallet_id`	Yes	Wallet ID to pause

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.14.8Oct 27, 2026
- addedInput schema / properties / wallet_id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / wallet_id / minimum
```
Added value: +-9007199254740991
```
First observedv1.7.3Mar 11, 2026

TDQS

A3.8/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. It discloses the key effect that no transactions can be signed while paused, which is valuable context, but it does not explain reversibility, required permissions, or what happens to pending transactions.

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?

The description is two short sentences with zero waste, and the core action is front-loaded before the consequence. Every sentence earns its place.

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 simple one-parameter mutation tool with no output schema, the description adequately states the core behavior and its immediate effect. Minor gaps remain around reversibility and return behavior, but the essential information is present.

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 description coverage is 100% and the single wallet_id parameter is already documented as 'Wallet ID to pause' in the schema. The description adds no additional parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Emergency pause a wallet') that clearly distinguishes it from sibling tools like unpause_wallet and delete_wallet. An agent can identify exactly what operation this tool performs.

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 word 'Emergency' implies urgency and a particular use case, but the description does not explicitly state when to choose this over unpause_wallet or delete_wallet, nor does it mention any prerequisites. Usage is only implied.

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