zFinia Intelligence

Base Token Metadata

base_token_metadata

Read a Base token name, symbol, decimals and total supply in one call. Handles tokens that return a bytes32 name or symbol instead of a string, which is the case that breaks naive decoders. Fields the contract does not implement come back null and are listed, rather than guessed at. Refuses an address with no contract. Pay 6000 atomic USDC on Base via exact x402. MCP does not pay; it provides a challenge handoff.

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

Input Schema

Name	Required	Description	Default
`token`	Yes	Token contract address.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses bytes32 decoding, null-for-unimplemented fields, refusal of non-contract addresses, and the 6000 atomic USDC x402 charge with an explicit note that MCP does not pay but hands off a challenge. Errors beyond the refusal case and retry/pagination behavior are not covered, so it falls short of a 5.

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 purpose is front-loaded in the first sentence, and the decoding edge case, null semantics, refusal rule and payment terms each add distinct information. It is dense but every sentence carries decision-relevant content.

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

Completeness5/5

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

No output schema exists, yet the description enumerates the returned fields, explains nulls, and states the payment handoff mechanism, which is the main failure mode for this tool. An agent has everything needed to call it and interpret the result.

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 coverage is 100% for the single `token` parameter, so the pattern and example already define the format. The description adds only the behavioral nuance that addresses without a contract are rejected, which is useful but not a substantial extension of parameter meaning.

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?

The first sentence names a specific verb and resource: read a Base token's name, symbol, decimals and total supply in one call. That scope is unambiguous and distinct from every sibling (snapshots, page tools, x402 diagnostics), so an agent can select it without opening the schema.

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 read-metadata framing plus the note that a no-contract address is refused, which tells the agent what input qualifies. However, there is no explicit statement of when to prefer this over related tools or what to do when payment cannot be completed. Missing prerequisites and exclusions keep it at implied-only guidance.

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

All zFinia Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?