Skip to main content
Glama

get_events_by_block_number

Read-onlyIdempotent

Retrieve events emitted in a specific TRON block with pagination support for precise block targeting and complete event access.

Instructions

Get events emitted in a specific block. Supports pagination via limit and fingerprint. Preferred over get_events_of_latest_block when you need precise block targeting or full event retrieval.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "blockNumber": "<blockNumber>"
    },
    "name": "get_events_by_block_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events per page (default 20, max 200)
networkNoNetwork name. Defaults to mainnet.
blockNumberYesThe block number to query events for
fingerprintNoPagination token from previous response
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that results are paginated via limit and fingerprint, which the schema also states, and says nothing about ordering, default page behavior, or what happens when no events exist in the block.

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?

Two tight sentences, purpose front-loaded, no filler. The phrase "full event retrieval" is slightly vague and does work that a sharper criterion could do, keeping it just short of exemplary.

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 simple read-only, idempotent lookup with full schema coverage and no output schema, the description covers purpose, pagination, and the main alternative. Only the shape of returned events and pagination termination (e.g., absent fingerprint) are left implicit.

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 description coverage is 100%, so all five parameters are documented in the schema itself; the description merely echoes limit and fingerprint for pagination. It adds no meaning about network selection or the trade-off of onlyConfirmed beyond what the schema provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 emitted") constrained to "a specific block", and explicitly contrasts with get_events_of_latest_block. It does not clarify its relationship to the other event siblings (get_events_by_contract_address, get_events_by_transaction_id), so differentiation is partial rather than complete.

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

Usage Guidelines4/5

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

Gives an explicit alternative and the condition that selects this tool: prefer it over get_events_of_latest_block for "precise block targeting or full event retrieval." No when-not guidance and no routing versus the contract-address or transaction-id variants, but the primary confusion risk is addressed.

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