Skip to main content
Glama

BRAINIAC Base Chain Data

Get ERC-20 total supply

chain-data_token_erc20-total-supply

Retrieve the total supply of an ERC-20 token on Base Mainnet using eth_call. Price $0.01 USDC. POST /api/v1/chain-data/token/erc20-total-supply. Unpaid calls return 402 and do not run.

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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "chain-data_token_erc20-total-supply"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockNumberNo
tokenAddressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: it names the chain, the underlying eth_call, the paid endpoint, and the 402 failure mode for unpaid calls. However, it says nothing about return format (a uint256 value, decimals handling), rate limiting, or what happens with an unknown token address or unfinalized block.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, purpose front-loaded, no filler. Pricing and the 402 behavior are stated plainly rather than buried.

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

Completeness3/5

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

For a simple two-parameter read with no output schema, the description covers invocation context well but leaves the blockNumber default and the shape of the returned supply value unexplained. Adequate to call the tool, not complete enough to interpret results confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it does not: neither tokenAddress nor blockNumber is mentioned. Critically, the default behavior when blockNumber is omitted (presumably latest) is undocumented, which changes results meaningfully for this kind of call.

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 ("Retrieve") and a precise resource ("total supply of an ERC-20 token"), plus the chain (Base Mainnet) and mechanism (eth_call). This distinguishes it from the erc20-balance and token_metadata siblings purely from the text.

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

Usage Guidelines2/5

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

The description never says when to use this versus erc20-balance, token_metadata, or contract_read, nor when a historical blockNumber is appropriate. The only operational context given is payment/pricing, which is not selection guidance.

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