Skip to main content
Glama

ERC-20 token risk scan (owner, proxy, liquidity)

token_scan
Read-only

Heuristic risk screen of an ERC-20 token on Base, Ethereum, Arbitrum, OP Mainnet, Polygon or Avalanche: name, symbol, supply; owner and renounce status; proxy and upgradeability; Sourcify verification; privileged functions in bytecode or verified ABI (mint, pause, blacklist, fee, limit, trading switch); Uniswap v2/v3 and Aerodrome pools with USD depth; risk score 0-100 with a reason per flag. Sources: on-chain reads via PublicNode JSON-RPC, Sourcify. Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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

Input Schema

NameRequiredDescriptionDefault
chainYesChain of the token: base (8453), ethereum (1), arbitrum (42161), optimism (10), polygon (137), avalanche (43114). Chain ids and aliases such as eth, arb, op, matic, avax are also accepted.
addressYesToken contract address (0x followed by 40 hex characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description earns credit for disclosing data sources (PublicNode JSON-RPC, Sourcify) and the cost model ($0.01 per successful call in USDC via x402 v2, failures and no-match calls free), which the annotations do not convey. It stops short of noting rate limits, coverage gaps on unverified contracts, or latency.

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?

Dense and front-loaded: the capability statement leads, followed by checked properties, then sources and pricing. It is a single long clause chain, which costs some scanability, but nearly every clause carries information and nothing is filler.

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?

With no output schema, the description carries the return-value burden and does it: it names the token metadata, ownership, proxy, verification, privileged-function flags, pool liquidity with USD depth, and the 0-100 score with per-flag reasons. Cost and billing behavior are also covered, leaving no material gap for a two-parameter read tool.

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

Parameters4/5

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

Schema coverage is 100% for both parameters, with chain enum and address format fully documented in the schema, so the baseline applies. The description adds only chain-level context that duplicates the schema enum and gives no extra semantics for the address parameter, so it lands at baseline.

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?

States a specific verb ('Heuristic risk screen') and resource ('ERC-20 token'), enumerates the chains and the exact dimensions checked (owner/renounce, proxy, Sourcify verification, privileged functions, Uniswap/Aerodrome pool depth, 0-100 score). That enumeration makes it clearly distinct from the price-oriented sibling token_price without needing to name it.

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 scope implies when it applies (pre-trade or pre-interaction risk checks on six named chains), and the pricing line hints at cost-conscious use. But there is no explicit when-to-use/when-not guidance and no routing to alternatives such as token_price, contract_abi, or wallet_balances.

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