Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Eth call, Ethereum contract call

eth_call
Read-only

Read-only contract call on Ethereum (eth_call) at the latest block, without a transaction or gas: send ABI-encoded calldata, or a function signature such as balanceOf(address) with args and the call is encoded and its result decoded for you. Use to read any view function that has no dedicated tool (the example reads USDC totalSupply). Calldata up to 8 KB; a call that reverts is 422 with the reason, uncharged. Example: to=0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48, data=0x18160ddd. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "to": "<to>",
      "data": "<data>"
    },
    "name": "eth_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes0x contract address to call
argsNoArguments for a function signature in data: comma separated, or a JSON array for arrays and tuples
dataYes0x ABI-encoded calldata (4-byte selector plus arguments), or a function signature: totalSupply(), balanceOf(address), or with its result types, balanceOf(address) returns (uint256)
fromNoOptional 0x sender address for calls that check msg.sender
returnsNoResult types to decode when data is a signature without them, for example uint256 or address,uint8

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint, openWorldHint, non-idempotent) by disclosing a calldata size cap (8 KB), revert behavior (422 with reason, uncharged), and pricing model ($0.01/call via x402 or card key, first 25 free, failed calls free). It also warns that repeats are not free, which explains why idempotentHint is false despite being a pure read.

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?

Front-loaded with the operation and chain, then usage, then limits and pricing, which is the right order for an agent. Slight redundancy around billing ("uncharged," "failed calls free," and "each call is charged") repeats the same point in three places.

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

Completeness5/5

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

No output schema exists, yet the description covers result decoding, error semantics, input size limits, and cost, which is everything needed to call it correctly. The absence of a block parameter is resolved by stating it always targets the latest block.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all five parameters and the baseline is 3. The description adds real value by explaining the data/args/returns interaction — that a signature plus separate args gets encoded and the result decoded — backed by a worked to/data example.

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 and resource plus the underlying RPC method ("Read-only contract call on Ethereum (eth_call) at the latest block, without a transaction or gas"), and the chain qualifier separates it from base_call/arb_call/op_call siblings. The example (USDC totalSupply at 0x18160ddd) makes the intended operation concrete.

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

Usage Guidelines4/5

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

Gives explicit routing guidance: "Use to read any view function that has no dedicated tool," which implicitly excludes eth_token_balance/eth_balance-style siblings without naming them. Clear context, but the exclusion is generic rather than pointing at the specific alternative tools an agent should prefer.

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.