Skip to main content
Glama

ERC-20 Token Rugpull & Honeypot Scanner

ingravity_scanTokenRugpullAndHoneypot
Read-onlyIdempotent

Audit ERC-20 tokens for rugpull and honeypot risks by disassembling live bytecode and inspecting proxies across five EVM chains, with no Solidity source required.

Instructions

Calls /api/v1/token-rug-scanner ($0.12 Full / $0.04 Essential USDC via x402 v2) to audit ERC-20 tokens via live 5-EVM RPC bytecode disassembly & proxy inspection (no Solidity source required).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ingravity_scanTokenRugpullAndHoneypot"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional Solidity source code for pre-deploy or hybrid AST scan.
tierNoFULL
chainIdNo
tokenNameNoOptional token label.
tokenAddressNoDeployed ERC-20 token address (0x...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With annotations already declaring readOnly/idempotent/non-destructive, the description's real contribution is disclosing the paid x402 v2 cost ($0.12 FULL / $0.04 ESSENTIAL USDC) and that it executes live RPC calls against five EVMs — meaningful cost and side-effect context an agent would not otherwise have. It stops short of saying what the scan returns or whether results are cached/rate-limited, and nothing in it contradicts the read-only annotations.

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 with no filler; the endpoint path, price tiers, and method are all packed in the right order. It is dense with nested parentheses and slightly run-on, which costs a point on readability but not on waste.

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?

For a scan tool with no output schema, the description should say what the audit produces (risk verdict, honeypot flags, bytecode findings) and clarify when tokenAddress vs code is needed; it does neither. The pricing and method disclosure are good, but an agent cannot predict the response shape or the argument combination required.

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 coverage is 60%, so the baseline is 3. The pricing parenthetical does add real meaning to the 'tier' enum (FULL=$0.12, ESSENTIAL=$0.04), but the description says nothing about chainId, tokenAddress, or the fact that zero parameters are required even though a scan presumably needs a tokenAddress or code — a notable ambiguity it does not resolve.

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 gives a specific verb and resource ('audit ERC-20 tokens') plus the mechanism (live 5-EVM RPC bytecode disassembly & proxy inspection, no Solidity source required), which is far more than a restatement of the name. It does not, however, contrast itself with the clearly adjacent siblings like auditSolidityContract or fastPingAddressSafety, so an agent still has to infer which scanner applies.

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?

Usage is only implied: 'no Solidity source required' signals this is for deployed/bytecode-only tokens as opposed to source-based auditing, and the schema's optional 'code' param for 'pre-deploy' hints at a second mode. There is no explicit when-to-use / when-not-to-use statement and no named alternative, so selection guidance is left to inference.

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