Skip to main content
Glama

get_events_by_contract_address

Read-only

Retrieve recent events emitted by a specific TRON contract address, with optional filters for event name, network, confirmation status, and pagination.

Instructions

Get recent events emitted by a specific contract address.

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": {
      "contractAddress": "<contractAddress>"
    },
    "name": "get_events_by_contract_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events per page (default 20, max 200)
networkNoNetwork name. Defaults to mainnet.
orderByNoSort order
eventNameNoFilter by event name (e.g. Transfer)
fingerprintNoPagination token from previous response
onlyConfirmedNoOnly return confirmed events
contractAddressYesThe contract address (base58 or hex)

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

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=false and destructiveHint=false, so the description needs to add operational context such as rate limits, pagination behavior, or result volume. It adds none of that, and the word 'recent' is left undefined even though the schema exposes a fingerprint pagination token and ascending sort, implying traversal beyond recent data.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, which is good. For a tool with seven parameters, paging, and network selection, one bare sentence is under-specified rather than efficiently concise.

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

Completeness2/5

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

The tool is a paginated, open-world, multi-parameter query with no output schema, so the description carries the burden of explaining result shape and paging flow. It says nothing about pagination via fingerprint, page size defaults, or what an emitted event record contains, leaving significant gaps for correct invocation.

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 seven parameters (limit, network, orderBy, eventName, fingerprint, onlyConfirmed, contractAddress) are already documented with defaults and formats. The description contributes no additional parameter meaning such as default-contract scope or event-name matching semantics, 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 recent events') scoped to 'a specific contract address', which clearly separates it from address-, block-, and transaction-oriented siblings in the catalog. It does not name any sibling explicitly, but the scoping qualifier does the disambiguating work.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of the alternatives (get_events_by_block_number, get_events_by_transaction_id, get_events_of_latest_block) that an agent would need to choose between. The only hint is the word 'recent', which is not framed as a selection criterion.

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