Skip to main content
Glama

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

Eth call, Optimism contract call

op_call
Read-only

Read-only contract call on Optimism (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=0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85, 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": "op_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?

Beyond the annotations it discloses the block context (latest), the 8 KB calldata ceiling, the revert behaviour (422 with reason, uncharged), and the full pricing model including the 25 free calls and that repeats are charged — which explains the idempotentHint=false. It also confirms no state change, consistent with readOnlyHint=true.

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 what it is and how to call it, then limits, error behaviour, and pricing — a sensible order. Slightly verbose at the tail, where 'Reads or computes only and changes nothing' restates the opening 'Read-only' and the readOnlyHint annotation.

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?

For a pay-per-call, no-output-schema tool, the description covers cost, free tier, size limit, failure semantics, and result decoding — everything an agent needs to call it correctly and predict the outcome. Nothing material is left to inference.

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 already 100%, so baseline is 3, but the description adds the governing workflow: pass raw ABI calldata OR a signature like balanceOf(address) with args, and the service encodes and decodes for you. That explains how data, args and returns interoperate in a way the per-field schema text only partially conveys.

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 ('Read-only contract call on Optimism (eth_call) at the latest block') and pins the chain, which is what separates it from the eth_call/arb_call/base_call siblings. It also names the capability boundary ('any view function that has no dedicated tool'), so an agent can place it immediately.

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 a clear selection rule: use for view functions that have no dedicated tool, implying op_token_balance/op_balance/etc. should be preferred where they exist. It stops short of naming any alternative explicitly and says nothing about when a dedicated tool would be better for the same read.

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.