Skip to main content
Glama

chainread__gas

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

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

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. Changed2 schema fields changed
    • 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. 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"
      -}
  5. First observed

TDQS

C2.4/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 genuinely useful behavior: x402 payment in USDC on Base (eip155:8453) via params._meta["x402/payment"], a stated cost, and a free live preview endpoint. However it omits rate limits, whether calls are read-only and idempotent, and what a successful response contains, and it repeats the price twice without adding detail.

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 comma-spliced catalog of nine unrelated capabilities, and the $0.01 price is stated twice in different phrasings. The endpoint URL and payment scheme are front-loaded only after the generic list, so the single tool-specific fact never gets emphasis.

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?

There is no output schema, so the description should explain the return shape and units (gwei vs wei, single value vs per-chain map), yet it says nothing about results. For a paid call an agent must decide on, the definition leaves the deliverable and the parameter-to-route mapping unspecified.

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 baseline is 3; the description adds only 'GET with query params'. The supplied parameter descriptions are keyed to other routes (/tx, /txpreflight, /ens), so nothing explains which of hash, name, chain, or address actually affects a gas read.

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 a whole family of operations (balance, gas, nonce, block, token metadata, tx, verdict, simulation, preflight) rather than stating what this specific tool returns. It never says 'gas' means gas price/estimate, for which chain, or in what unit, so an agent cannot distinguish it from chainread__balance or chainread__block using the text alone.

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 describes the transport (HTTP GET with query params), the price, and a free preview, but gives no when-to-use or when-not-to-use guidance and never names a sibling to route against. An agent learns how to pay, not when this call is the right one.

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