Skip to main content
Glama

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

Eth call, Base contract call

base_call
Read-only

Read-only contract call on Base (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=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, 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": "base_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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, idempotentHint=false, so the bar is lower, yet the description adds real operational context: an 8 KB calldata cap, a 422 with the revert reason on failure, and the fact that failed calls are uncharged. It also explains the non-idempotent annotation in practical terms ('each call is charged, so repeats are not free') and surfaces the x402/card-key auth requirement. The only gap is that pricing details are repeated ('uncharged' vs 'failed calls free'), slightly muddying rather than adding clarity.

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?

It is front-loaded with the core operation and its constraints, then the example, then pricing, which is a sensible order and dense without filler. The minor cost is redundancy between 'a call that reverts is 422 with the reason, uncharged' and the later 'failed calls free', which restates the same guarantee.

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 stateless read tool with no output schema, the description covers everything an agent needs: input modes, size limit, error behavior, decoding of results, cost model, and a fully worked example with address and calldata. Nothing material is missing before a correct first invocation.

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 baseline is 3 and each parameter (to, data, args, from, returns) is already documented in the schema. The description adds the useful dual-mode concept that data may be raw ABI calldata or a bare signature whose args are supplied separately and whose result is auto-decoded, but it does not explain the returns/args interplay beyond what the schema already states.

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?

The description names a specific verb and resource ('Read-only contract call on Base (eth_call)') and pins the execution context ('at the latest block, without a transaction or gas'). It also scopes itself against the sibling set: 'Use to read any view function that has no dedicated tool', with a concrete USDC totalSupply example. An agent can distinguish this from base_token_balance, base_allowance, or base_storage without opening a schema.

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?

It states the selection condition clearly ('any view function that has no dedicated tool') and gives a worked example of when this applies. It stops short of naming the specific sibling to prefer for common reads (token balances, allowances), leaving that inference to the agent, so this is strong but not fully explicit routing.

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.