Skip to main content
Glama

chainread__batch

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/batch

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__batch"
  }
}

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. Changed3 schema fields changed
    • removedInput schema / properties / addresses
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / chain
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / ops
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "address": {
      +        "type": "string"
      +      },
      +      "op": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed2 schema fields changed
    • removedInput schema / properties / chain / enum
      Removed value: -[
      -  "base",
      -  "ethereum"
      -]
    • removedInput schema / required
      Removed value: -[
      -  "addresses"
      -]
  5. Added
  6. Removed
  7. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden, and it does disclose important operational facts an agent needs: it is a paid call ($0.01 USDC on Base), x402 payment is supplied via params._meta['x402/payment'], and the transport is GET against a concrete URL. However, it never explains what happens when multiple read types are requested at once, whether partial failures are returned, or any rate limits — gaps that matter for a batching tool.

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 capability list is front-loaded and useful, but the pricing is stated twice ('$0.01 per paid call' and the full 'Price: $0.01 per call in USDC on Base...') and the raw URL/curl-style payload is appended, making it read as stacked service boilerplate rather than a tight tool description.

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

Completeness2/5

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

For a four-parameter, zero-annotation, no-output-schema batch tool, the description leaves the core mechanics unexplained: how to express multiple reads, in what shape results come back, and how it relates to the numerous chainread single-resource siblings. Payment and endpoint details are covered, but the batching contract is not.

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 the schema already documents hash, name, chain, and address with their relevant endpoints. The description adds only 'GET with query params', which does not clarify how these four optional parameters interact in a batch context (e.g., whether one call can combine address + chain + hash).

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

Purpose3/5

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

The description names the resource family ('Live Base/Ethereum chain reads') and enumerates the read types (balance, gas, nonce, block, token metadata, tx, verdict/risk, simulation, preflight), so an agent knows it hits on-chain data. But for a tool explicitly named 'batch', it never says what is being batched or how this differs from single-resource siblings like chainread__balance or chainread__multiread — the text reads like service-level boilerplate rather than this tool's purpose.

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?

There is no guidance on when to choose this over the many single-purpose chainread siblings or over agentkit__batch/txpreflight__batch. The only usage-adjacent information is the free '/preview' mention and the payment requirement, which is about cost, not about selecting this tool.

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