Skip to main content
Glama

BRAINIAC Base Chain Data

Get token metadata

chain-data_token_metadata

Retrieve ERC-20 name, symbol, decimals, and total supply for a token on Base Mainnet where supported. Price $0.02 USDC. POST /api/v1/chain-data/token/metadata. 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_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockNumberNo
tokenAddressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description still discloses meaningful behavior beyond the schema: pay-per-call at $0.02 USDC, a POST endpoint, and that unpaid calls return 402 and do not execute. It stops short of noting rate limits, caching, or whether an unsupported token returns empty versus error.

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 short sentences, front-loaded with capability, then cost, then failure mode. Each sentence carries information; the raw endpoint path is the only content an agent arguably does not need.

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?

Return fields are enumerated, which compensates for the absent output schema, and the payment behavior is covered. However, with zero schema description coverage and no annotations, the unexplained blockNumber parameter and the vague 'where supported' leave real gaps for a paid call.

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 carry parameter meaning and largely does not. It never explains that blockNumber pins the query to a historical block, nor restates the required 0x-prefixed address format; 'on Base Mainnet' is the only parameter-adjacent detail.

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?

Names a specific verb and resource set ('Retrieve ERC-20 name, symbol, decimals, and total supply') scoped to Base Mainnet, which separates it from balance/transfer siblings. It does not name the near-duplicate sibling chain-data_token_erc20-total-supply, so an agent must infer the overlap itself.

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?

The 'where supported' qualifier hints at a precondition, and the 402 note tells the agent a paid call can fail, but there is no explicit guidance on when to prefer this over chain-data_token_erc20-total-supply or erc20-balance. Usage is implied by subject matter rather than stated.

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