Skip to main content
Glama

Check an ERC-20 token's facts, proxy, owner and risks

evm_token
Read-only

On-chain facts about an ERC-20 contract on Base (default), Ethereum, Arbitrum, Optimism or Polygon, read over RPC: name, symbol, decimals, total supply, code size, whether it is a proxy (EIP-1967, EIP-1822 or the pre-1967 OpenZeppelin slots) with its implementation and admin, owner() and whether ownership is renounced, risky functions found in the bytecode, and plain warning flags. No paid security service is called. Related tools on this server, for a different need: evm_nft when you need ERC-721 facts for one token: owner, collection name; evm_balance when you need ERC-20 balance of an address for one token contract. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls 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": {
      "address": "<address>"
    },
    "name": "evm_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, arbitrum, optimism or polygon
addressYesToken contract address, 0x…

Output Schema

NameRequiredDescriptionDefault
nameNo
noteNo
chainNo
flagsNo
ownerNo
proxyNo
symbolNo
addressNo
hasCodeNo
sourcesNo
decimalsNo
checkedAtNo
codeBytesNo
disclaimerNo
codeScannedNo
totalSupplyNo
riskyFunctionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "address": {},
      +    "chain": {},
      +    "checkedAt": {},
      +    "codeBytes": {},
      +    "codeScanned": {},
      +    "decimals": {},
      +    "disclaimer": {},
      +    "flags": {},
      +    "hasCode": {},
      +    "name": {},
      +    "note": {},
      +    "owner": {},
      +    "proxy": {},
      +    "riskyFunctions": {},
      +    "sources": {},
      +    "symbol": {},
      +    "totalSupply": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/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 partly covered. The description adds genuinely useful context beyond them: reads happen over RPC, no paid security service is called, pricing is $0.003 per successful call via x402, and failed calls are not charged. It does not discuss rate limits or what happens on unsupported chains, but the cost and failure semantics are the important disclosures here.

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?

Purpose and return fields are front-loaded, followed by sibling routing and then pricing, which is logical. The long enumeration of returned fields overlaps with the output schema and makes the paragraph heavier than necessary, but no sentence is pure 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?

Given an output schema exists, the description needn't specify return shape, yet it still states the chain coverage, the read mechanism, the cost model, and failure charging. Combined with the annotations, an agent has everything needed to call this correctly and predict the cost.

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%, and every parameter is documented there, including 'base (default)'. The description's mention of the five supported chains and the Base default repeats rather than extends the schema. With the schema doing the heavy lifting, 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?

Opens with a specific verb+resource: on-chain facts about an ERC-20 contract, listing the concrete fields returned (name, symbol, decimals, supply, code size, proxy status, owner, risky functions). It explicitly distinguishes itself from evm_nft (ERC-721) and evm_balance (per-address balances), so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Names the two nearest alternatives and the condition that selects each ('evm_nft when you need ERC-721 facts for one token', 'evm_balance when you need ERC-20 balance of an address'). It also states the default chain and the supported chain set, leaving little to inference for choosing this tool.

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