Skip to main content
Glama

EVM block number (x402)

get_chain_block_number

Read-onlyIdempotent

The current chain tip (latest block height) via eth_blockNumber, across Base, Ethereum, Optimism, Arbitrum, Polygon, Gnosis. The freshness read settlement, indexing and trading agents poll to know where the chain is. Live public RPC; one paid call.

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

Input Schema

NameRequiredDescriptionDefault
x_paymentNoSigned x402 payment payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the description's added value is in the operational details: the data is live from a public RPC, the value is freshness-sensitive (polled), and each invocation costs one paid call. The paid-call disclosure is meaningful for an agent that must supply x_payment. Return shape (an integer height) is only implied.

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?

Three tight sentences with the core definition front-loaded, then usage, then operational cost — no filler. The middle sentence is slightly awkwardly phrased ('The freshness read settlement, indexing and trading agents poll to know...') but still carries information.

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

Completeness3/5

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

For a zero-required-parameter read tool with no output schema, the description covers the return concept (latest block height) and chain coverage. The notable gap is that six chains are listed but the schema exposes no chain selector, leaving it unclear how an agent targets a specific chain (server default? payment payload?). That ambiguity matters for correct invocation.

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?

There is a single parameter, x_payment, fully described in the schema (100% coverage). The description's 'one paid call' line contextualizes why that parameter exists and that it is required in practice, which is genuine added meaning beyond the schema's bare field description. No format or error-handling detail for the payment payload is added.

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?

Names a precise resource and scope: the current chain tip (latest block height), plus the underlying method (eth_blockNumber) and the six supported chains. It is clearly a read of the latest height rather than a block lookup, though it never explicitly contrasts with the close sibling chain_block_header, so sibling differentiation is implied rather than stated.

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?

Gives concrete usage context: it is the freshness read that settlement, indexing and trading agents poll to know where the chain is. That tells an agent the right situation to call it. It does not state exclusions or point to chain_block_header for historical/per-block reads, so it stops short of full alternatives 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