Skip to main content
Glama

EVM & Solana Chain Reads (Tanod)

get_block_number

Read-onlyIdempotent

chainpeek: Get the latest block number, timestamp and age in seconds of Ethereum, Base or Robinhood Chain. For the full header use get_block; for chain id and gas price use get_chain_info. Returns the latest block. One RPC read. Ethereum, Base and Robinhood only. Read-only. Reads are cached up to 30 s. A bad chain is a 422 before any payment (not charged). Typically under 1 s. Price: USD 0.001. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/ethereum-rpc-reads-api.html

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

Input Schema

NameRequiredDescriptionDefault
chainYesethereum, base or robinhood (Robinhood Chain, chain id 4663).

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
block_timeNo
age_secondsNo
block_numberNo
block_timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / chain / title
      Removed value: -"Chain"
    • removedInput schema / title
      Removed value: -"get_block_numberArguments"
  2. Changed2 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum or base."New value: +"ethereum, base or robinhood (Robinhood Chain, chain id 4663)."
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "robinhood"
      +]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), it discloses caching up to 30 s, typical sub-second latency, the 422-before-payment failure mode, price, and the 10-free-reads-per-IP-per-day quota. Those are exactly the operational facts an agent needs to plan retries and cost.

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 the sibling routing, then operational facts in short fragments. The pricing, quota and docs URL are justified for a paid API but make the tail feel like a rate card rather than tool guidance.

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

Completeness5/5

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

An output schema exists, so return-shape detail is not required, and the description still summarizes the returned fields. For a one-parameter read tool, nothing an agent needs to invoke it correctly — scope, alternatives, cost, failure mode — is missing.

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% and the enum already documents the three chain values, so the baseline is 3. The description still adds value by clarifying that Robinhood Chain is chain id 4663 (in the schema) and, more importantly, that an invalid chain returns 422 without charge — error semantics the schema does not express.

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 ('Get the latest block number, timestamp and age in seconds') and scopes it to three named chains. It explicitly separates itself from get_block and get_chain_info, so an agent can pick the right tool without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: use get_block for the full header, get_chain_info for chain id and gas price. It also states the supported chains and that an unsupported chain fails as a 422 before payment, which tells the agent when the call is safe to attempt.

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.