Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

ERC-20 token info on Base: name, symbol, decimals, total supply

chain_token
Read-only

ERC-20 token metadata for one contract on Base mainnet: name, symbol, decimals, and total supply (human-readable and raw), with a flag for whether it behaves like an ERC-20 at all and whether it is native USDC. Handles older tokens that return bytes32 names. Useful for formatting token amounts correctly and spotting look-alike tokens. Read-only. Not charged for an invalid address or an address with no contract. Paid via x402; see list_prices.

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": {
      "address": "<address>"
    },
    "name": "chain_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesToken contract 0x address on Base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses important behavior: payment via x402, no charge for invalid or contract-less addresses, handling of older bytes32-name tokens, and flags for ERC-20 behavior and native USDC. These details materially help an agent invoke the tool correctly.

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 description is front-loaded with the core metadata fields and remains focused. It is slightly dense and includes a redundant 'Read-only' statement, but each element generally serves a purpose.

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?

Given the absence of an output schema, the description successfully explains what is returned: name, symbol, decimals, total supply in human-readable and raw forms, plus behavior and USDC flags. It also covers edge cases and payment behavior, making it complete for invocation.

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%, so the parameter is already documented in the schema. The description reinforces that the address is for a token contract on Base mainnet but adds little semantic detail beyond the schema itself.

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 description states a specific resource and scope: ERC-20 token metadata for one contract on Base mainnet, including the exact fields returned. It is easily distinguishable from sibling tools like chain_balance, chain_tx, and chain_contract.

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

Usage Guidelines4/5

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

It gives clear usage context by saying the tool is useful for formatting token amounts correctly and spotting look-alike tokens. It does not explicitly name alternatives or when-not-to-use cases, but the intended context is clear.

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

All VerifyLite toolsInspect
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