Skip to main content
Glama

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

Optimism block number

op_block
Read-only

Latest block number and block details on Optimism, 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 op_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": "op_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoBlock number, or 'latest' (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, open-world, non-idempotent, non-destructive, so the bar is lower; the description still adds real value with the 422 response for non-existent blocks, the uncharged-on-failure rule, and the per-call pricing model. The closing sentence about reads/computes and repeat charges largely restates readOnlyHint and idempotentHint=false, which caps it below a 5.

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 capability and the sibling routing are front-loaded, and every clause is short. It is somewhat packed with pricing and failure semantics, and the final sentence duplicates what annotations already say.

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?

With no output schema, the description carries the return-shape burden and does so by naming hash, timestamp, transaction count, gas used and limit, base fee in gwei, and producer. Error behavior and cost are also covered, so nothing an agent needs before calling 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%, so the baseline is 3; the description adds format detail ('any block by decimal number'), the 'latest' default, and a concrete example value. That is modest but genuine meaning beyond the schema.

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: latest block number and block details on Optimism, or any block by number, then enumerates the returned fields. It explicitly routes fee lookups to op_gas, so an agent can separate it from the sibling 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 positive use cases (timestamps, confirmation counts) and an explicit alternative with its condition (current fees → op_gas). The example 'number=latest' anchors the default usage.

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.