Skip to main content
Glama

get_events_of_latest_block

Read-only

Retrieves events from the current event-bearing block, skipping empty blocks. Supports network selection and confirmed-only filtering for event monitoring.

Instructions

Get events from the most recent block that contains events (skips empty blocks). Results may be limited by the API default page size and subject to event indexing lag. For precise control, use get_events_by_block_number with a specific block number and limit/fingerprint pagination.

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_events_of_latest_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
onlyConfirmedNoOnly return confirmed events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false) and open-world behavior, but the description adds genuinely new context: results are capped by the API default page size, and event indexing lag can make the data stale. It doesn't explain how to work around the page-size cap (e.g. whether a fingerprint cursor is available on this tool), which keeps it short of 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.

Conciseness5/5

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

Three short sentences ordered from scope, to caveats, to the escape hatch to a sibling. Nothing is redundant and no sentence could be dropped without losing information.

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 two-optional-parameter read tool with no output schema and safety already declared by annotations, the description covers scope, staleness, and truncation risk adequately. It stops short of describing the returned event shape or how the default page size is surfaced, minor gaps given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters (network, onlyConfirmed) are documented in the schema itself. The description adds no semantics for either – notably it never mentions that onlyConfirmed exists or how it interacts with 'latest block' – so it sits at the baseline for a fully-documented 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 ('Get events') plus precise scope ('most recent block that contains events, skips empty blocks'), which immediately separates it from get_events_by_block_number and get_latest_block. The parenthetical about skipping empty blocks removes the main ambiguity about what 'latest' means here.

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?

Explicitly names the alternative tool and the condition that selects it: use get_events_by_block_number when you need a specific block number and limit/fingerprint pagination. The implicit converse – use this tool when you just want whatever is newest – is clear from the first sentence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools