Skip to main content
Glama

chainread__token

Live Base/Ethereum chain reads for AI agents over x402: balance, gas, nonce, block, token metadata, tx, address verdict/risk, simulation and tx preflight. GET with query params. $0.01 per paid call; free live preview at /preview. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/chainread/token

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chainread__token"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashNo0x transaction hash (for /tx, /txpreflight)
nameNoENS name (for /ens)
chainNobase or ethereum
addressNo0x address or token contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"0x address or token contract"
    • addedInput schema / properties / chain / description
      Added value: +"base or ethereum"
    • addedInput schema / properties / hash
      Added value: +{
      +  "description": "0x transaction hash (for /tx, /txpreflight)",
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "ENS name (for /ens)",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / chain
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / ops
      Removed value: -{
      -  "items": {
      -    "properties": {
      -      "address": {
      -        "type": "string"
      -      },
      -      "op": {
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
  3. Changed4 schema fields changed
    • removedInput schema / properties / chain
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / data
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / ops
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "address": {
      +        "type": "string"
      +      },
      +      "op": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / to
      Removed value: -{
      -  "type": "string"
      -}
  4. Changed3 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / data
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "type": "string"
      +}
  5. Changed5 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"0x address or ERC-20 contract address"
    • removedInput schema / properties / addresses
      Removed value: -{
      -  "description": "Up to 25 addresses (for /batch)",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / chain / enum
      Removed value: -[
      -  "base",
      -  "ethereum"
      -]
    • removedInput schema / properties / hash
      Removed value: -{
      -  "description": "0x transaction hash (for /tx)",
      -  "type": "string"
      -}
    • removedInput schema / properties / number
      Removed value: -{
      -  "description": "Block number or 'latest' (for /block)",
      -  "type": "string"
      -}
  6. First observed

TDQS

C2.6/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 disclose meaningful behavior: paid calls cost $0.01 in USDC on Base via x402, payment must be supplied in params._meta['x402/payment'], and a free preview exists. What it omits is token-specific behavior — what metadata is returned, how missing/optional params are handled, or failure modes — so it is partial rather than complete.

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

Conciseness2/5

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

The opening sentence is a product pitch rather than a statement of this tool's function, and the pricing is repeated twice ('$0.01 per paid call' then 'Price: $0.01 per call in USDC on Base'). The actual tool scope is buried at the end behind transport and billing details.

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?

For a four-parameter, no-output-schema read tool, the definition does cover the operational essentials an agent needs to invoke it: HTTP method, endpoint, payment requirement and preview option. The remaining gap is tool-specific scope versus its many siblings, which is a purpose issue more than a completeness one.

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 description coverage is 100%, so hash, name, chain and address are already documented in the schema, establishing a baseline of 3. The description adds one genuinely new semantic — the x402 payment parameter location — but says nothing about how the four declared params route between the implied endpoints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates an entire service catalog — 'balance, gas, nonce, block, token metadata, tx, address verdict/risk, simulation and tx preflight' — rather than stating what chainread__token itself does. Those capabilities map to sibling tools (chainread__balance, chainread__gas, chainread__tx), so an agent cannot determine this tool's specific verb+resource from the text. Only the name and the trailing URL hint at token metadata.

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?

It explains transport (GET with query params) and the free /preview alternative, which is useful, but gives no guidance on when to choose chainread__token over chainread__tokenreport, chainread__balance, or the token_dd__* tools. No exclusions or selection criteria are 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