Skip to main content
Glama

chainread__network

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

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

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. Changed2 schema fields changed
    • 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
      Removed value: -{
      -  "description": "0x address or ERC-20 contract address",
      -  "type": "string"
      -}
    • 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.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose genuinely useful operational facts — GET method, base URL, $0.01 USDC on Base pricing, the x402 payment field params._meta["x402/payment"], and a free /preview endpoint — which is real value. However it omits what happens when payment is absent (error vs free tier), whether reads are side-effect free, any rate limits, and, critically, how a single tool with only hash/name/chain/address dispatches to the nine listed capabilities; the URL ends in /network while the parameter descriptions reference /tx, /ens and /txpreflight, with no explanation of that discrepancy.

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 dense, which suits a gateway tool, but pricing is stated twice ("$0.01 per paid call" then "Price: $0.01 per call in USDC on Base") and the trailing raw URL duplicates what is already implied. The sentence "GET with query params" is too thin to justify its place given the routing ambiguity it leaves unresolved.

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 tool that advertises nine distinct read capabilities with no output schema and no annotations, the definition should explain how inputs map to capabilities and what each returns at a high level. Instead the agent is left with four optional parameters and an endpoint ending in /network that does not obviously correspond to any listed operation, so it cannot confidently construct a call.

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% and each parameter already documents its role and the sub-path it serves (hash for /tx and /txpreflight, name for /ens, address for address or token contract). The description adds nothing beyond the schema — it does not clarify how chain selection interacts with the other parameters or which combinations are valid. Baseline 3 applies when the schema does the work.

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 a resource domain ("Live Base/Ethereum chain reads") and enumerates capabilities (balance, gas, nonce, block, token metadata, tx, verdict, simulation, preflight), but that enumeration is a superset that duplicates nearly every sibling tool (chainread__balance, chainread__gas, chainread__nonce, chainread__block, chainread__token, chainread__tx, chainread__verdict, chainread__simulate, chainread__txpreflight). It never states what this tool itself uniquely is (a multiplexer? a router?) or how one call selects among those capabilities, leaving the agent unable to distinguish it from the specific siblings.

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 when-to-use guidance at all: nothing says whether to prefer this umbrella tool over chainread__balance or chainread__gas, nor under what circumstances the free /preview versus a paid call should be used. The only conditional information is a pricing mention, which is about cost, not about tool selection.

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