Skip to main content
Glama

Evm block

evm_block
Read-onlyIdempotent

Latest block and gas price across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): block number, time and age in seconds, gas price and base fee in gwei, transaction count, chain id. $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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "evm_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.7/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 open-world, so the safety profile is covered. The description adds materially useful details those annotations cannot convey: the $0.001 per-call price, the x402 settlement assets (USDC on Arc/Base/Solana, XNT on X1), and that passing a signed payment completes the purchase inside the same call. It stops short of failure, expiry, or rate-limit behavior.

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?

Two sentences, front-loaded with what the tool returns and followed by the payment mechanics. The payment sentence is dense with parenthetical currency detail but every clause carries actionable information; nothing is padded.

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 compensates by enumerating the response fields (block number, time and age, gas price, base fee, tx count, chain id). Combined with cost and payment workflow disclosure, an agent has nearly everything needed, with only error/expiry handling unstated.

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 coverage is 100% and both parameters are documented in-schema, so the baseline is 3. The description reinforces the `payment` semantics by explaining the sign-and-resubmit cycle and confirms the chain set, but adds little about `chain` beyond the enum list already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope ('Latest block and gas price across 8 EVM chains') and enumerates the returned fields, which lets an agent distinguish it from history-oriented siblings like block_at_time. It does not name that sibling explicitly, so differentiation is implicit rather than spelled out.

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

Usage Guidelines3/5

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

The two-call x402 flow ('call once without payment for the terms, sign them..., call again with payment') is clear procedural guidance an agent can act on. However, there is no guidance on when to prefer this over block_at_time or gas_all, and no mention of prerequisites such as wallet funding beyond the currency list.

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