Skip to main content
Glama

x420_chain_token-metadata

Read ERC-20 token metadata—name, symbol, decimals, and totalSupply—from a Base mainnet contract via public RPC. Returns JSON plus signed receipt and settlement transaction.

Instructions

Base token metadata: name, symbol, decimals and totalSupply of an ERC-20 contract on Base mainnet, read from the contract through the public RPC. Source: Base mainnet RPC. Says nothing about legitimacy. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.02 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: address, name, symbol, decimals, total_supply - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"token":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}.

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": "x420_chain_token-metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes0x ERC-20 contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior3/5

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

The description adds substantial context beyond the annotations: the data source (public RPC), the cost ($0.02 USDC per call, real money), the settlement mechanism (x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY), and that the response includes a signed receipt and settlement transaction. That explains why readOnlyHint is false despite a read-only data fetch, so there is no contradiction. Score held at 3 only because the boilerplate disclaimer consumes space without adding behavioral information.

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

Conciseness3/5

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

The functional content is front-loaded and compact, but the long legal/advice disclaimer is boilerplate that does not help an agent select or invoke the tool. The payment and return-value sentences earn their place; the disclaimer does not.

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 carries the burden of explaining returns, and it does list the JSON fields plus receipt and settlement transaction. It is nearly complete, missing only failure behavior (non-contract address, RPC revert, insufficient funds for the paid call).

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

Parameters4/5

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

Only one parameter, and schema coverage is 100%, so the schema already defines 'token' as a 0x ERC-20 contract address. The description reinforces this with a concrete example input containing a real Base USDC address, which removes any ambiguity about address format or chain.

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: reads name, symbol, decimals and totalSupply of an ERC-20 contract on Base mainnet via the public RPC. The scope (Base mainnet, ERC-20, public RPC) is precise enough that an agent can distinguish it from wallet-balance or gas-estimate siblings without inspecting their schemas.

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 is implied by the purpose (call it to learn a token's on-chain metadata), and the caveat 'Says nothing about legitimacy' usefully scopes what the result means. However, there is no explicit when-to-use/when-not guidance and no named alternative for related questions such as balances or pricing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.