Skip to main content
Glama

Token supply and market cap (x402)

chain_token_supply

Read-onlyIdempotent

$0.01 via x402: total supply, holder count, decimals, and live USD price / market cap for any ERC-20/721 token contract, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The supply read trading, valuation and risk agents make to size circulating supply, dilution and holder distribution before pricing or trading a token. Live from Blockscout; one paid call instead of running your own RPC.

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": "chain_token_supply"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase|ethereum|optimism|arbitrum|polygon|gnosis (default ethereum)
addressYesToken contract address (0x...)
x_paymentNox402 payment payload (base64) to settle this call; omit to receive the payment terms first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, yet the description adds material facts the annotations cannot: a $0.01 x402 cost, that omitting x_payment returns payment terms first, and that data is live from Blockscout. It does not describe rate limits, failure modes, or what a token without a market (no price/market cap) returns.

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?

The core capability and chain scope are front-loaded, and the price/payment model is stated early. The middle sentence about 'trading, valuation and risk agents' is somewhat promotional but still conveys usage context, so it mostly earns its place.

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?

With no output schema, the description correctly enumerates the returned fields (supply, holders, decimals, price, market cap) and explains the two-step payment handshake. Missing are any notes on how values are computed or how the response differs for ERC-721 versus ERC-20 tokens, which is the main remaining gap.

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 chain, address and x_payment are already documented in the schema, and the description only echoes the chain list and the payment-omission behavior. Baseline 3 is appropriate since the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and result set: total supply, holder count, decimals, USD price and market cap for any ERC-20/721 contract across six named chains. An agent can tell exactly what it returns, though it never names a sibling tool it should be preferred over (e.g. dex_token_data or chain_token_identity).

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?

It gives clear context for use ('before pricing or trading a token', to size circulating supply, dilution and holder distribution) and an explicit alternative it replaces ('one paid call instead of running your own RPC'). It does not state when NOT to use it or which sibling to pick instead, which keeps it below a 5.

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