Skip to main content
Glama

drain_signer

Transfer a KMS signer's entire native-token balance to any address, even if the signer is suspended. Uses a safety valve pattern to recover funds.

Instructions

Drain a KMS signer's entire native-token balance to a destination address. Works on suspended signers — the safety valve. Cost: chain gas + $0.000005 KMS sign fee.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signer_idYesThe KMS signer ID
project_idYesThe project ID
destination_addressYesWhere to send the entire native-token balance. Cost: chain gas + $0.000005 KMS sign fee. Works on suspended signers.
Behavior3/5

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

Discloses it drains entire balance, works on suspended signers, and includes cost. However, with no annotations, it misses details like irreversibility, required permissions, or post-drain state of the signer.

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?

Two sentences: first states action and condition, second states cost. No unnecessary words, front-loaded.

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?

Covers action, condition, and cost but lacks details on return value, side effects, permissions, or reversibility. Adequate for a straightforward fund-draining tool but not fully complete.

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 covers all 3 parameters with descriptions. Description adds cost and the 'suspended' condition but repeats schema content. Baseline 3 as schema does heavy lifting.

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 specific verb 'drain' and resource 'KMS signer's entire native-token balance'. It mentions 'safety valve' for suspended signers, clearly distinguishing it from sibling tools like delete_signer, list_signers, etc.

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?

States 'Works on suspended signers — the safety valve', giving explicit context for when to use. Includes cost information. Does not explicitly state when not to use or list alternatives, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MajorTal/run402'

If you have feedback or need assistance with the MCP directory API, please join our Discord server