Skip to main content
Glama

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

Arbitrum block number

arb_block
Read-only

Latest block number and block details on Arbitrum One, 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 arb_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": "arb_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoBlock number, or 'latest' (default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds real value beyond them: a 422 error for nonexistent blocks that is uncharged, and a per-call price model with a free tier and free failures, which explains why repeats are not free. However, pricing/commercial boilerplate occupies most of that added text and no rate-limit or latency behavior is described, keeping it at a solid but not exceptional 3.

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 capability and return fields before the routing hint and example, which is the right order for an agent. It is dense and largely earns its words, but the pricing/free-tier clause is longer than an agent needs for tool selection and could be trimmed without losing decision-relevant information.

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?

For a single optional parameter and no output schema, the description covers the full picture: what is returned (hash, timestamp, tx count, gas used/limit, base fee, producer), the accepted input forms including default, the failure mode, and the cost model. Nothing required to call it correctly 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, but the description adds meaning the schema lacks: the block identifier must be a decimal number (a real disambiguation versus hex-encoded IDs common on chain APIs) and it restates 'latest' as the accepted default with an example. That is genuine semantic value on top of an already complete 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 and resource ('Latest block number and block details on Arbitrum One') plus an alternate mode ('any block by decimal number'), and names the chain explicitly so it is distinguishable from the many sibling *_block tools. It even enumerates the returned fields, so an agent knows exactly what it gets.

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?

Provides explicit when-to-use guidance ('Use for timestamps and confirmation counts') and an explicit exclusion with the alternative that covers it ('for current fees use arb_gas'). It also supplies a concrete invocation example (number=latest), leaving nothing to inference.

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.