Skip to main content
Glama

get_latest_block

Paid $0.01 (x402, USDC Base): latest Base mainnet block height (eth_blockNumber via public RPC). Cheapest chain-tip probe for agents.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most consequential trait: this is a paid call ($0.01 via x402 in USDC on Base), which an agent must budget for and which implies a payment challenge on the call path. It also identifies the data source as a public RPC. It stops short of describing failure modes, latency, or what a payment rejection looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact line plus a short positioning tagline, with the cost and payment rail front-loaded ahead of what is returned. Nothing is padded and every clause contributes (price, rail, resource, scope, method, use case).

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

Completeness4/5

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

For a no-parameter, no-output-schema tool the description covers cost, source, and subject matter, which is enough to call it correctly. The one real gap is the return type: eth_blockNumber yields a hex quantity, and an agent is not told whether it receives an integer or a hex string.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The parenthetical naming the backing RPC method is the only parameter-adjacent detail and it is a helpful anchor.

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 and scope: 'latest Base mainnet block height', plus the exact underlying RPC method (eth_blockNumber). That combination separates it from siblings like get_base_gas or get_coin_convert without requiring the schema to be opened.

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

Usage Guidelines3/5

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

'Cheapest chain-tip probe for agents' implies the scenario (a cheap chain-head lookup), but the description never explicitly says when to prefer this over adjacent tools such as get_base_gas, nor does it name any exclusion. Usage is inferable rather than stated.

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.

Resources