Skip to main content
Glama

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

Eth call, Arbitrum contract call

arb_call
Read-only

Read-only contract call on Arbitrum One (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=0xaf88d065e77c8cC2239327C5EDb3A432268e5831, 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": "arb_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?

Annotations already mark it read-only, open-world, non-idempotent, and non-destructive, but the description goes well beyond them: latest-block semantics, an 8 KB calldata cap, revert behavior as an uncharged 422 with the reason, and an explicit pricing model ($0.01/call via x402 or card key, first 25 free, failed calls free). The note that each call is charged and repeats are not free explains the idempotentHint=false annotation rather than merely repeating it.

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?

Information is front-loaded: what it does, how to invoke it, when to use it, then constraints, pricing, and an example. It is dense but each clause carries operational weight; only the pricing sentence is slightly heavy relative to invocation-critical content.

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 low-complexity read tool with no output schema and full schema coverage, the description supplies everything needed: encoding mode, block semantics, size limits, error shape, and cost. An agent can call it correctly and predict the response without further context.

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 baseline is 3; the description still adds useful meaning by framing the two modes of `data` (raw ABI-encoded calldata vs. a bare function signature that gets encoded/decoded automatically) and by supplying a concrete to/data pair. It does not elaborate on `from`, `returns`, or the comma-separated vs. JSON-array `args` convention beyond what the schema already says.

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 eth_call on Arbitrum One) plus scope (latest block, no transaction or gas). It also carves out its niche against the sibling family by saying it is for view functions with 'no dedicated tool', which separates it from arb_balance, arb_token_balance, eth_call, and the other chain-specific call tools.

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 routing rule: use this for any view function lacking a dedicated tool, with USDC totalSupply as a worked example. It does not explicitly exclude cases (e.g. when arb_balance or arb_token_balance should be preferred), leaving the agent to infer the dedicated-tool mapping from sibling names.

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.