Crank Protocol

kill_wallet

Destructive

Emergency freeze an agent wallet.

Sets status=killed so the policy gate refuses every subsequent value-bearing action. Returns confirmation + a frozen-positions count. (Turnkey scoped-key revocation is handled by the deferred provisioning ticket.)

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_address": "<wallet_address>"
    },
    "name": "kill_wallet"
  }
}

Input Schema

Name	Required	Description	Default
`caller_id`	No
`wallet_address`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description explains the mechanism (sets status=killed), the downstream effect (policy gate refuses value-bearing actions), and the output (confirmation + frozen-positions count). It also discloses a limitation (scoped-key revocation is not handled here). This goes beyond the annotations (destructiveHint=true, idempotentHint=false) by adding concrete behavioral context. No contradiction.

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 three sentences with no fluff. The first sentence front-loads the purpose, and the rest delivers essential behavioral detail. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity and the presence of annotations and an output schema, the description covers all necessary dimensions: purpose, exact effect, return value, and an alternative. It is comprehensive for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a schema description coverage of 0%, the description carries full burden for parameter guidance, but it does not mention wallet_address or caller_id at all. The wallet_address is partially implied by "agent wallet," but the optional caller_id remains unexplained. This is a clear gap given the zero coverage.

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 opens with a specific, actionable verb phrase: "Emergency freeze an agent wallet." It distinguishes the tool from siblings like enable_agent_wallet, create_agent_wallet, and wallet_status by specifying the freeze action and the mechanism (sets status=killed).

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 clearly frames this as an emergency operation, implying a high-stakes context. The note about scoped-key revocation being handled by a deferred provisioning ticket provides an explicit alternative for a related but distinct action, helping the agent decide when not to use this tool. However, it does not explicitly list exclusions or contrast with wallet_status/enable_agent_wallet.

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

All Crank Protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?