Skip to main content
Glama

An EVM block by number, or the latest one: hash, time

evm_block
Read-only

An EVM block by number, or the latest one: hash, time, transaction count, gas used and limit, and base fee in gwei. Read over public RPC. Related tools on this server, for a different need: evm_address when you need native balance, nonce and account type of an EVM address; evm_allowance when you need to check an ERC-20 allowance granted to a spender. 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

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
chainNobase (default), ethereum, arbitrum, optimism or polygon
numberNoBlock number, or latest (default)

Output Schema

NameRequiredDescriptionDefault
hashNo
timeNo
chainNo
numberNo
sourceNo
gasUsedNo
gasLimitNo
checkedAtNo
disclaimerNo
baseFeeGweiNo
transactionCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuine context beyond them: reads go over public RPC, each successful call costs $0.002 via x402 (USDC on Base, Solana, and 10+ networks), and failed calls are free. That payment/auth detail is exactly the kind of behavioral fact an agent needs before calling. Rate limits and pagination are unaddressed.

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 useful capabilities are front-loaded in one sentence, followed by the sibling routing and pricing. The pricing clause is dense but factual and each element contributes; 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?

For a simple two-param read with an output schema, the definition covers scope, defaults, cost model, and alternatives — enough for correct invocation. Only marginal gaps remain, such as response shape hints for unusual blocks or RPC failure behavior.

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%, so both parameters (chain, number) are already fully documented, including their defaults. The description restates the 'latest' default but adds no new parameter meaning, so the baseline 3 applies.

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 names the resource precisely (an EVM block by number or latest) and enumerates the returned fields: hash, time, transaction count, gas used/limit, base fee in gwei. It is clearly distinguishable from siblings, though the leading phrase is noun-style rather than an explicit verb, so it stops just short of a 5.

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 gives an explicit routing rule with two named alternatives ('evm_address when you need native balance, nonce and account type' and 'evm_allowance when you need to check an ERC-20 allowance'), plus stated defaults for chain and block number. It does not cover other plausible alternatives such as evm_tx or evm_logs, so no explicit when-not guidance.

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