Skip to main content
Glama

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

Base block number

base_block
Read-only

Latest block number and block details on Base, 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 base_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": "base_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?

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), but the description adds material context beyond them: a nonexistent block returns 422 and is uncharged, price is $0.002/call via x402 USDC or a card key, the first 25 calls free, failed calls free, and repeat calls are billed again. That billing-per-call note also explains why idempotentHint is false in practice.

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 payload contents, then usage, then error behavior, then pricing – a sensible order with no filler. Minor redundancy: pricing is stated twice ('Price $0.002/call... first 25 free; failed calls free' and 'each call is charged, so repeats are not free') and 'Reads or computes only and changes nothing' restates readOnlyHint.

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 one-parameter, no-output-schema read tool at 100% schema coverage, this is complete: return fields, default behavior, failure mode, and cost are all stated. No annotation flag (openWorldHint, idempotentHint) is left unexplained.

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 single parameter is already documented, so baseline would be 3. The description adds that the number must be decimal (implying hex is not accepted) and supplies a concrete example, which is meaningful format guidance beyond the schema's terse 'Block number, or latest (default)'.

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 resource (Base block) and enumerates what comes back: hash, timestamp, transaction count, gas used/limit, base fee in gwei, producer. 'on Base' combined with the explicit pointer to base_gas makes it distinguishable from both the fee sibling and the other chain block tools.

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 usage ('Use for timestamps and confirmation counts') and an explicit exclusion with the correct alternative ('for current fees use base_gas'). It also states the default case via the example number=latest, so an agent knows it can call with no arguments to get the head block.

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.