Skip to main content
Glama

Evm call

evm_call
Read-onlyIdempotent

Read-only contract call (eth_call) across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): returned bytes or the revert reason, at a named block. Nothing is signed or sent. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "evm_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYescontract address (0x...)
dataYeshex calldata: 4-byte selector plus ABI-encoded arguments
fromNooptional caller address
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum (default), base, arc or bnb"New value: +"ethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces that with "Nothing is signed or sent," then adds genuinely new behavior: per-call pricing ($0.001), accepted payment assets and chains, and the two-step pay-per-call handshake. One inconsistency: "at a named block" implies a block-selection parameter that does not exist in the schema, which could mislead an agent looking to pin a block.

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?

The capability and read-only guarantee are front-loaded, then chains, output, and pricing follow in a logical order. It is dense but every sentence carries operational weight; the payment sentence is clause-heavy and could be tightened without losing meaning.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and does so (bytes or revert reason). Pricing, payment flow, and supported chains are all covered for a 5-parameter read tool. The only real gap is the unexplained "named block" reference and no note on behavior when the call reverts versus when payment is invalid.

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 earns above that by explaining the `payment` parameter as the second half of a round-trip (first call returns terms, second call carries the signed payload) and by enumerating the accepted `chain` values including Arc and Robinhood. The lingering "named block" phrasing adds a semantic expectation the schema cannot satisfy.

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?

"Read-only contract call (eth_call) across 8 EVM chains" gives a specific verb and resource, plus the exact RPC primitive it wraps, which immediately separates it from siblings like evm_code, evm_tx, or evm_balances_bulk. The clause "returned bytes or the revert reason" pins down the output shape so an agent knows what it gets.

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?

The description explicitly prescribes the invocation sequence: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. That is real, actionable guidance. What is absent is when to prefer this over siblings such as evm_code (for bytecode) or evm_tx (for transaction data), so there are no explicit exclusions.

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