Skip to main content
Glama

chainread__code

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

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

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.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well on payment and transport: it discloses GET over HTTP, the concrete endpoint URL, the $0.01 USDC price on Base (eip155:8453), x402 payment placement in params._meta["x402/payment"], and a free preview path. Those are exactly the auth/cost facts an agent needs before calling a paid endpoint. It stops short of describing error behavior, defaults, or what a hallucinated operation path returns, which keeps it below 5.

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 description is front-loaded with the purpose and then lists capabilities, cost, payment location, and raw HTTP details. Several elements are dense and repetitious — price is stated twice ($0.01 per paid call and again as 'Price: $0.01 per call in USDC on Base'), and the bare URL line is appended without structure. It is compact overall but mixes purpose, pricing, and transport without clear separation.

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 paid, unannotated tool with no output schema sitting among ~20 overlapping siblings, the description omits the two things an agent most needs: how to select an operation (no path/operation parameter exists in the schema despite references to /tx, /ens, /txpreflight) and what a read returns. The cost/auth story is covered, but the core invocation model is not, so it is insufficient at this complexity.

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, including hints tying hash to /tx and /txpreflight. The description does not explain the most important semantic question raised by its own text: how the enumerated operations (balance, gas, nonce) map onto four parameters that contain no operation/path selector. Baseline 3 applies since the schema does the parameter-level 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 opening states a resource ('Live Base/Ethereum chain reads') but then lists eight different operations (balance, gas, nonce, block, token, tx, verdict, simulate, preflight) rather than one specific verb+resource. Those operations each have a dedicated sibling (chainread__balance, chainread__gas, chainread__tx, chainread__verdict, etc.), so the description reads as an API-wide summary rather than a distinct tool contract, and the agent cannot tell what this tool uniquely does. It is vague rather than tautological, so a 3 is appropriate.

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 statement of when to use chainread__code versus the many sibling tools that cover the same capabilities. The description mentions a free /preview endpoint and per-call pricing, which are payment mechanics, not selection guidance. Nothing tells the agent which of the listed operations this tool actually routes to or when it should be preferred.

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