Skip to main content
Glama

Get decoded event logs

zenith_get_logs
Read-only

Fetches decoded event logs for a contract or event across a block range by walking chunks newest to oldest; use nextToBlock to continue beyond the RPC's 1,000-block limit.

Instructions

Event logs for a contract and/or event over any block range, decoded. The public RPC only serves 1,000 blocks per call and has no filters or WebSockets, so the range is walked in chunks from newest to oldest; use nextToBlock to continue. Defaults to the last 1,000 blocks.

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

Input Schema

NameRequiredDescriptionDefault
eventNoEvent signature, e.g. "Transfer(address indexed from, address indexed to, uint256 value)"
addressNoEVM address (0x…)
maxLogsNo
toBlockNo
fromBlockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds real value by disclosing that the public RPC caps at 1,000 blocks per call, lacks filters and WebSockets, and that the range is scanned newest-to-oldest with continuation via nextToBlock. The phrase 'has no filters' is slightly confusing next to the tool's own event/address parameters, and return format or rate-limit behavior is never described.

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 sentences, front-loaded with the what and then the operational constraints; every clause carries information. The second sentence is dense and the 'no filters' remark muddies rather than clarifies.

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

Completeness3/5

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

With no output schema, 40% parameter coverage and five all-optional parameters, the description does well on pagination but leaves the shape of decoded log results, the interaction of maxLogs with chunking, and boundary behavior unspecified. Adequate to call correctly, but not complete.

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 only 40%, so the description should compensate more than it does; it explains the default block range (relevant to fromBlock/toBlock) but adds no meaning to event, address, or maxLogs beyond the schema. Notably it references nextToBlock, which is not in the input schema, implying a response field in a tool with no output schema.

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?

The description names a specific resource (decoded event logs) and scope (per contract and/or event, any block range), which is far more than the title alone conveys. It does not explicitly contrast itself with siblings like zenith_get_transaction or zenith_read_contract, so sibling differentiation is left implicit.

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?

It gives useful operational guidance: the default is the last 1,000 blocks, and nextToBlock should be used to continue walking older ranges. It offers no when-not guidance and never names an alternative tool for cases where decoded logs are the wrong approach.

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