Skip to main content
Glama

Token Risk Evm

token_risk_evm
Read-onlyIdempotent

Rug-pull / honeypot / scam RISK SCREENING for an EVM token (Ethereum, BSC, Base, Arbitrum, Polygon, Optimism, Avalanche, and more). Pass the token CONTRACT ADDRESS and the chain. Detects honeypots (can you actually sell?), buy/sell tax, mintable supply, hidden/renounceable owner, owner-can-change-balances, blacklist/whitelist controls, proxy/upgradeable code, unverified source, and holder concentration, the standard rug-pull red flags. Returns a computed red_flags[] list plus the raw GoPlus Security facts. Keyless, live on-chain. Use before buying/interacting with any token, or for "is $TOKEN a scam / honeypot / safe?".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "ethereum",
      "contract_address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
    },
    "name": "token_risk_evm"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain name (ethereum, bsc, base, arbitrum, polygon, optimism, avalanche, ...) or a numeric GoPlus chain_id. Default ethereum.
contract_addressYesThe token contract address (0x...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"Chain name (ethereum, bsc, base, arbitrum, polygon, optimism, avalanche, …) or a numeric GoPlus chain_id. Default ethereum."New value: +"Chain name (ethereum, bsc, base, arbitrum, polygon, optimism, avalanche, ...) or a numeric GoPlus chain_id. Default ethereum."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial context on top: keyless operation, live on-chain data, the underlying data source (GoPlus Security), and the return shape (computed red_flags[] plus raw facts). The enumerated detection categories tell the agent exactly what questions the tool can answer.

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?

Front-loaded with the core purpose, then progressively adds scope, call instructions, detection list, and return shape. Dense but every clause is informative; the long mid-sentence enumeration of red flags is the only part that borders on over-stuffing.

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 burden of explaining returns and does so ('computed red_flags[] list plus the raw GoPlus Security facts'). For a two-parameter read-only screening tool, nothing an agent needs in order to call it correctly is missing.

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 100%, so both parameters are already documented, including the chain list and the ethereum default. The description reinforces that the address must be the token CONTRACT ADDRESS (not a pair or pool) and that chain must accompany it, but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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 and resource ('RISK SCREENING for an EVM token'), names the supported chains, and enumerates the exact classes of risk detected. It is immediately distinguishable from token_risk_solana by the EVM scope, so an agent can route without opening the schema.

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?

Gives explicit when-to-use guidance: 'Use before buying/interacting with any token' and for 'is $TOKEN a scam / honeypot / safe?' questions. It does not state when NOT to use it or name the non-EVM alternative, but the EVM scoping makes the boundary largely self-evident.

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.