Skip to main content
Glama

Evm token info

evm_token_info
Read-onlyIdempotent

Token info and total supply for any ERC20 across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): name, symbol, decimals, total supply. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "token": "<token>"
    },
    "name": "evm_token_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
tokenYesERC20 contract (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum (default), base, arc or bnb"New value: +"ethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, open-world read, and the description adds material context beyond that: the $0.001 per-call price, the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), the x402 protocol, and the two-step challenge/settlement handshake. That is precisely the auth and cost information an agent needs before invoking a paid endpoint.

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?

Three tight sentences leading with the capability and chain coverage before the cost and payment mechanics. The final sentence slightly restates the schema's description of `payment`, but every clause carries actionable information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid read endpoint with no output schema, the description covers what is returned, which chains are supported, what it costs, and how to complete payment. Minor gaps remain around failure behavior when a payment is rejected or how supply values are formatted, but nothing essential for a correct call is absent.

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%, so baseline is 3; the description adds genuine meaning for `payment` by explaining it is the signed x402 payload equivalent to a PAYMENT-SIGNATURE header and that passing it completes the purchase inline. It also confirms the default chain is Ethereum through the listed chain ordering, though it adds nothing new for `token` beyond the schema's 0x contract hint.

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 pair: retrieves token info and total supply for ERC20 contracts, enumerates the eight supported chains, and names the exact fields returned (name, symbol, decimals, total supply). This clearly separates it from evm_token_balance, which returns holdings rather than contract metadata.

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 sequencing for the paid path: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. It lacks any statement about when to prefer this over sibling lookups like base_token_price or evm_token_balance, but the operational guidance it does give is unambiguous.

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