Skip to main content
Glama

ChainGuard Vault — Solana Rent & 8-Chain EVM Dust Recovery

scan_evm_dust_and_hygiene

Zero-connect multi-chain EVM wallet scan (Base/Arbitrum/Optimism/Polygon/Ethereum) finding sweepable ERC-20 dust in USD, EIP-7702 hijacks, and open unlimited approvals.

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": {
      "address": "<address>"
    },
    "name": "scan_evm_dust_and_hygiene"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
networksNobase,arbitrum,optimism,polygon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose meaningful behavior beyond the name: the scan is read-only in effect ('zero-connect'), covers five named chains, and returns findings denominated in USD. It does not state permissions, rate limits, cost, or whether results are paginated or cached, leaving real gaps for a no-annotation tool.

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?

A single dense sentence with the scope front-loaded and no filler. The jargon ('sweepable ERC-20 dust', 'EIP-7702 hijacks') is domain-appropriate rather than wasteful, though the parenthetical chain list makes it slightly heavy to parse.

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?

With no annotations, no output schema, and 0% parameter coverage, the description needs to do more work than it does. It adequately conveys what is scanned and what categories of findings come back, but leaves the return shape, address format, and networks encoding undocumented.

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?

Schema description coverage is 0% for both parameters, so the description must compensate and only partly does. It names the supported chains, which maps loosely to the 'networks' parameter, but never says the value is a comma-separated string, never reconciles that Ethereum is listed here while the default omits it, and never describes the required 'address' format.

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 states a specific verb and resource ('multi-chain EVM wallet scan') and enumerates the three findings it produces (sweepable ERC-20 dust in USD, EIP-7702 hijacks, open unlimited approvals), which clearly separates it from siblings like build_evm_dust_to_usdt_sweep or check_eip7702_delegation. It stops short of explicitly naming a sibling to route against, so a 4 rather than 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. 'Zero-connect' hints that no wallet connection is required, which is a useful usage signal, but the agent must infer that this is the broad survey tool versus the single-purpose check_* siblings.

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