Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Total supply of an ERC-20 or ERC-721 token

eth_token_supply
Read-only

Total supply of an ERC-20 or ERC-721 token contract via totalSupply (eth_call), with name, symbol and decimals and the human-readable amount. Ethereum mainnet, public RPC data. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/eth/token-supply

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

Input Schema

NameRequiredDescriptionDefault
tokenYesToken contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the underlying call mechanism (eth_call on totalSupply), the network (mainnet), and the payment model ($0.001 USDC per call via x402 v2 on Base) plus a free demo endpoint — genuinely useful invocation context. It stops short of stating failure behavior, e.g. what happens for a non-contract or non-token address, or when name/symbol metadata is absent.

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 contents are front-loaded, with network and pricing trailing. The pricing URL and x402 details are dense but earn their place; the description is a single flowing block rather than cleanly separated clauses, which costs a little readability.

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?

There is no output schema, and the description compensates well by enumerating the returned fields (name, symbol, decimals, human-readable amount) as well as network and cost. The remaining gap is edge-case behavior for invalid or non-token addresses, which an agent would want to know before calling.

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?

Only one parameter exists and schema description coverage is 100%, with an explicit address pattern, so the schema already carries the semantics. The description adds only the notion that the address is a token contract (as opposed to a wallet), which is marginal added value.

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 names a specific resource (ERC-20/ERC-721 token contract) and result (totalSupply via eth_call, plus name, symbol, decimals, human-readable amount), so the agent knows exactly what comes back. It does not explicitly contrast with the sibling eth_token_balance, but the 'total supply' framing makes the scope distinguishable.

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

Usage Guidelines3/5

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

Usage context is implied by the scope constraints ('Ethereum mainnet, public RPC data'), which tells the agent this is for mainnet tokens only. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as the balance tool for holder-specific queries.

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