Skip to main content
Glama

BRAINIAC Base Chain Data

Execute read-only contract call

chain-data_contract_read

Execute a read-only call to a smart contract on Base Mainnet using eth_call. Returns the result without submitting a transaction. Price $0.02 USDC. POST /api/v1/chain-data/contract/read. Unpaid calls return 402 and do not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>",
      "data": "<data>"
    },
    "name": "chain-data_contract_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
addressYes
blockNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the chain, the read-only nature, absence of a submitted transaction, the price ($0.02 USDC), the transport (POST endpoint), and the failure mode (unpaid calls return 402 and do not run). It omits revert/error behavior for failing calls and whether a blockNumber default applies, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and mechanism, then the return contract, then cost and payment semantics. Nothing is padded, though the raw endpoint path ('POST /api/v1/chain-data/contract/read') is arguably transport trivia that displaces parameter guidance.

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

Completeness3/5

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

Given zero annotations, no output schema, and 0% parameter coverage, the description adequately covers payment/auth and side-effect profile but leaves the response shape unexplained ('Returns the result' — a hex string? decoded?) and says nothing about the three parameters. For a tool this low-level, an agent still has to guess how to construct and interpret the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain address, data, and blockNumber — but it explains none of them. Only the term 'eth_call' indirectly hints at calldata semantics, and the important question of what blockNumber defaults to (latest vs a pinned block) is left entirely unaddressed.

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

Purpose5/5

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

States a specific verb (Execute a read-only call), the exact resource (a smart contract on Base Mainnet via eth_call), and the key scope distinction from write paths ('Returns the result without submitting a transaction'). An agent can tell this is the generic arbitrary-call tool versus the single-purpose siblings like chain-data_token_erc20-balance or chain-data_contract_code.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'read-only' and 'without submitting a transaction', which tells the agent this is for non-mutating queries, and the 402 note tells it payment must be in place. However, there is no explicit when-to-use-vs-alternative guidance (e.g. prefer the dedicated ERC-20 balance tool over a hand-encoded eth_call) and no statement of what this tool is not for.

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