Skip to main content
Glama

Read multi-chain EVM JSON-RPC with fallback

rpc_evm
Read-only

Read-only JSON-RPC pass-through for 20+ EVM chains (ethereum, base, arbitrum, optimism, polygon, bsc, avalanche, gnosis, linea, scroll, zksync, mantle, blast, celo, fantom, sonic, unichain, opbnb, zora, mode, metis, cronos). Single or batch calls (up to 10). Write methods refused. Related tools on this server, for a different need: rpc_solana when you need to read Solana JSON-RPC mainnet methods with fallback. 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": {
      "chain": "<chain>"
    },
    "name": "rpc_evm"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchNoOptional batch of up to 10 { method, params } calls
chainYesTarget EVM chain name (e.g. ethereum, base, arbitrum)
methodNoJSON-RPC read method (e.g. eth_blockNumber, eth_call)
paramsNoJSON-RPC parameters array

Output Schema

NameRequiredDescriptionDefault
chainNo
sourceNo
chainIdNo
providerNo
responseNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, and the description is consistent while adding context the annotations cannot carry: write methods are refused, batch is capped at 10, cost is $0.002 per successful call via x402 in USDC on Base/Solana and 10 more networks, and failed calls are free. Pricing and failure-billing semantics are exactly the kind of detail an agent needs before invoking a paid tool.

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 the core purpose and constraints, then routing, then pricing — a sensible order. The inline list of 21 chain names is long but earns its place as the only enumeration of valid chain values since no enums exist; otherwise the prose is tight.

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 an output schema present, return values need not be explained, and annotations plus full schema coverage carry the structural load. The description closes the remaining gaps — cost, refusal of writes, batch limit, cross-chain scope — though it omits error/fallback behavior despite the title advertising fallback.

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 every parameter is already documented in structured form, and the batch cap of 10 is repeated from the schema. The description adds only the constraint that the method parameter must be a read method, which is useful but marginal; baseline 3 applies when the schema does the heavy lifting. The chain list does implicitly enumerate valid chain values, which has some value given zero enums.

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 JSON-RPC pass-through — and enumerates the exact 20+ EVM chains covered. It also names the sibling it is not (rpc_solana) with the condition that selects it, so the agent can route 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?

Explicitly covers single vs batch usage (up to 10) and states that write methods are refused, which is a clear when-not condition. It routes Solana needs to rpc_solana, but gives no guidance on when to use this raw pass-through versus the many evm_* helper siblings like evm_call or evm_block.

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