Skip to main content
Glama

Token facts read on chain: for an ERC-20 on 22 EVM chains

token_metadata
Read-only

Token facts read on chain: for an ERC-20 on 22 EVM chains the name, symbol, decimals, total supply and EIP-1967 proxy implementation; for a Solana SPL mint the decimals, supply, mint and freeze authority. Adds price and liquidity from the token's deepest DexScreener pool on that chain, its logo and websites, and whether the Uniswap default list carries it (EVM). Information only, not financial advice. Related tools on this server, for a different need: token_search when you need to search token contract addresses across chains by symbol. Price: $0.002 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": {
      "chain": "<chain>",
      "address": "<address>"
    },
    "name": "token_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYessolana, or an EVM chain: ethereum, base, arbitrum, optimism, polygon, bsc, avalanche, gnosis, linea, scroll, zksync, mantle, blast, celo, fantom, sonic, unichain, opbnb, zora, mode, metis, cronos
addressYesToken contract address (0x...) or Solana mint address

Output Schema

NameRequiredDescriptionDefault
nameNo
chainNo
marketNo
sourceNo
symbolNo
addressNo
logoUrlNo
decimalsNo
websitesNo
checkedAtNo
disclaimerNo
totalSupplyNo
totalSupplyRawNo
proxyImplementationNo
onUniswapDefaultListNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedOutput schema / properties / liquidityUsd
      Removed value: -{}
    • removedOutput schema / properties / listSource
      Removed value: -{}
    • addedOutput schema / properties / market
      Added value: +{}
    • removedOutput schema / properties / onMajorList
      Removed value: -{}
    • addedOutput schema / properties / onUniswapDefaultList
      Added value: +{}
    • removedOutput schema / properties / priceUsd
      Removed value: -{}
    • addedOutput schema / properties / proxyImplementation
      Added value: +{}
    • addedOutput schema / properties / totalSupply
      Added value: +{}
    • addedOutput schema / properties / totalSupplyRaw
      Added value: +{}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds substantial context: data provenance (price/liquidity from the token's deepest DexScreener pool on that chain), an EIP-1967 proxy lookup, a Uniswap default-list membership check, and the fact that non-EVM fields differ. It also discloses cost mechanics — $0.002 per successful call via x402 USDC on Base, Solana and 10 more networks, with failed calls not charged — which is exactly the kind of behavioral detail annotations cannot carry.

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 returned fields, then the related-tool pointer, then pricing — a sensible order. The first sentence is long and runs the ERC-20 and Solana field lists together, and the unpriced disclaimer sentence is filler, but almost every other clause carries information an agent needs.

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?

An output schema exists, so return shape need not be explained, and the description instead covers the things structured fields cannot: coverage of 22 EVM chains plus Solana, field differences per chain family, data source, an explicit sibling alternative, and the pay-per-call cost model with failure handling. Nothing an agent needs to select or invoke 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% and the chain parameter already lists every supported network, so the schema does the heavy lifting. The description adds only marginal meaning, notably that chain selection also determines which DexScreener pool supplies price, which is implied but not stated in the schema.

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 ("Token facts read on chain") and enumerates exactly what is returned per chain family: name, symbol, decimals, total supply and EIP-1967 proxy implementation for ERC-20s; decimals, supply, mint and freeze authority for Solana SPL mints. It also names the sibling it is not (token_search), so an agent can separate the two without opening either 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?

Explicitly routes one alternative: use token_search when searching contract addresses by symbol. Usage context (read-only enrichment, information only, not financial advice) is clear, but there is no guidance on when to prefer the narrower siblings whose names suggest overlapping scope (evm_token, solana_token), so the routing is partial rather than exhaustive.

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