Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Ethereum block number

eth_block
Read-only

Latest block number and block details on Ethereum, or any block by decimal number: hash, timestamp, transaction count, gas used and limit, base fee in gwei and producer. Use for timestamps and confirmation counts; for current fees use eth_gas. A block that does not exist yet returns 422, uncharged. Example: number=latest. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
numberNoBlock number, or 'latest' (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: a nonexistent block returns 422 uncharged, pricing is $0.002/call with 25 free calls and failed calls free, and repeats are not free. This also usefully explains why idempotentHint=false on an otherwise pure read — each invocation is billed.

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 purpose and return fields before pricing details; nearly every clause carries information. The billing/pricing sentences are dense but justified given they explain charging behavior absent from annotations. Slight density makes it harder to scan than a shorter definition.

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?

No output schema exists, so the description compensates by enumerating the returned fields, plus error behavior (422) and cost model. For a one-parameter read tool this covers everything an agent needs to call it correctly.

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%, so baseline is 3, but the description adds the important detail that the number is decimal (Ethereum APIs conventionally use hex) and gives a concrete example 'number=latest'. It does not state the expected format for out-of-range or pending blocks, but that is minor.

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+resource pair (fetch latest block number / any block by number) and enumerates the returned fields: hash, timestamp, transaction count, gas used and limit, base fee, producer. It explicitly contrasts itself with the sibling eth_gas, so an agent can route without opening either 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 concrete when-to-use cases ('for timestamps and confirmation counts') and names the alternative for a different need ('for current fees use eth_gas'). The only omission is the per-chain siblings (arb_block, base_block, etc.), which is acceptable since guidance is judged on the definition's own text.

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.