Skip to main content
Glama

Wallet Doctor

drainForensics

Read-only

Wallet activity review: last 25 transactions with status, failed txs flagged, plus current token delegates (for drain triage) — $0.0025 USDC per call via x402 v2 (Solana or Base).

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

Input Schema

NameRequiredDescriptionDefault
walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, and the description's read-only 'review' framing is consistent with them. It adds behavior the annotations cannot convey: the fixed 25-transaction window, that failed transactions are explicitly flagged, and the payment model ($0.0025 USDC per call via x402 v2 on Solana or Base), which is critical context before invocation.

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?

One front-loaded sentence delivers the payload contents first, then the triage use case, then the price. Dense but no wasted wording; the pricing clause is slightly crammed but still 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?

With no output schema, the description does the work of describing the return payload (transactions, statuses, flagged failures, delegates) and the cost per call. The remaining gap is chain/addressing semantics for the wallet argument, which matters for a tool that prices in two ecosystems.

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 0% for the single required 'wallet' parameter, so the description must compensate. It only implies that the argument identifies the wallet under review and gives no address format or chain-disambiguation guidance, despite the tool spanning Solana and Base.

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?

Names a concrete resource and scope: the last 25 transactions with statuses, flagged failures, and current token delegates. That is a specific read operation an agent can distinguish from approvals, balance, tokenSafety or txtrace, though the description never explicitly contrasts itself with those siblings.

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 parenthetical 'for drain triage' implies the investigative scenario in which this tool applies, which is useful context. However, there is no explicit when-to-use versus when-not, and no pointer to which sibling to call instead for plain balances or approval checks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources