Skip to main content
Glama

Read the result of a read-only EVM contract function

evm_call
Read-only

Read-only contract call (eth_call): decodes the return value of a function you name, e.g. balanceOf(address) returns (uint256). Nothing is signed or sent. A function whose name reads like a write (transfer, approve, mint, set...) is refused unless it is declared view or pure. Related tools on this server, for a different need: evm_balance when you need ERC-20 balance of an address for one token contract; evm_contract when you need to check whether an EVM contract is verified and its ABI. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "contract": "<contract>",
      "function": "<function>"
    },
    "name": "evm_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoJSON array of arguments, e.g. ["0xd8dA…"]
chainNobase (default), ethereum, arbitrum, optimism or polygon
contractYesContract address, 0x…
functionYesHuman-readable signature, e.g. balanceOf(address) returns (uint256)

Output Schema

NameRequiredDescriptionDefault
argsNo
chainNo
resultNo
sourceNo
outputsNo
contractNo
functionNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that nothing is signed or sent, that write-like names are refused unless view/pure, and that failures are not charged. It also explains the pricing model and payment networks, which is important behavioral context for a paid x402 tool.

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

Conciseness5/5

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

The description is front-loaded with the core operation and then adds only useful constraints, alternatives, and pricing. Each sentence earns its place by helping the agent decide whether and how to call the tool.

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?

Given the full schema coverage, existing output schema, and read-only annotation, the description supplies the remaining decision-critical context: safety, refusal behavior, sibling alternatives, and cost. Nothing essential for correct invocation is missing.

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%, and the description mostly repeats the same function-signature example already present in the schema. It does not add new meaning for args, chain defaults, or contract addressing, so the schema remains the primary source of parameter semantics.

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 states a specific verb and resource: read-only ETH contract call that decodes a named function's return value. It explicitly distinguishes this tool from evm_balance and evm_contract, so an agent can tell it apart from nearby alternatives without opening their schemas.

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

Usage Guidelines5/5

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

It gives clear usage conditions and names alternatives with the exact need each serves: evm_balance for a single ERC-20 balance and evm_contract for verification or ABI lookup. It also states a key exclusion: write-like function names are refused unless declared view or pure.

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