Skip to main content
Glama

chainread__balance

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

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

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 / address
      Removed value: -{
      -  "type": "string"
      -}
    • 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 / 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"
      -}
  5. 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 carries the full load, and it does disclose genuinely useful behavior: HTTP GET, the concrete endpoint, x402 payment in USDC on Base (eip155:8453), the $0.01 cost, and the free /preview path. However it never says what a call returns, whether a missing address errors or returns a zero balance, or whether the payment header is required only for live vs preview calls.

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 front-loaded sentence is a marketing feature dump for the whole API, most of which is irrelevant to a balance read and crowds out tool-specific information. The payment and endpoint details are well placed and compact, but several clauses earn no place in this tool's definition.

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?

A payment-gated tool with 4 parameters (0 required), no annotations, and no output schema needs the description to say which parameter actually identifies the account and what the response contains. It fails on both: it never clarifies whether 'address' is the account whose balance is read (and whether a token contract address yields a token balance), nor what happens when all params are omitted.

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 4 parameters are already self-documenting (hash, name, chain, address). The description adds no parameter meaning beyond 'Live Base/Ethereum', which the chain field's own description already states. Per-call cost is useful context but not parameter semantics. Baseline 3 applies.

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 is written at the API-family level, listing nine different operations (balance, gas, nonce, block, token metadata, tx, verdict, simulation, preflight) rather than stating what this specific tool returns. Only the trailing endpoint URL '.../chainread/balance' and the first item in the list tie it to balances. An agent can guess the purpose but must infer it from the name and URL, not from a stated verb+resource.

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 use this instead of siblings such as chainread__token (which likely covers token balances) or chainread__multiread, and no mention of chainread__payment/preview alternatives for avoiding a paid call. The only usage-adjacent content is pricing ($0.01/call, free /preview), which is a cost constraint rather than a selection rule.

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