Skip to main content
Glama

get_events_by_transaction_id

Read-onlyIdempotent

Retrieve all events emitted by a specific TRON transaction using its transaction ID, with optional network and confirmation filters.

Instructions

Get all events emitted by a specific transaction.

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": {
      "transactionId": "<transactionId>"
    },
    "name": "get_events_by_transaction_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.
onlyConfirmedNoOnly return confirmed events. Defaults to unset (both).
transactionIdYesThe transaction ID (hash) to query events for

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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without the description. The description adds nothing beyond that: it does not say whether results are paginated despite 'all events', what an event record contains, or anything about the openWorldHint behavior of querying an external network.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness borders on under-specification for a network-query tool.

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 only three params and full schema coverage, plus annotations covering read-only/idempotent semantics and no output schema expected, the basics are present. What's missing is anything about result shape or whether 'all events' is bounded, which matters for an open-world chain query.

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 all three parameters carry descriptions (transactionId, network default mainnet, onlyConfirmed default unset). The description adds no meaning beyond the schema — 'a specific transaction' merely restates the required transactionId — so baseline 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?

The description states a specific verb plus resource and scope: 'Get all events emitted by a specific transaction.' That distinguishes it functionally from get_events_by_block_number or get_events_by_contract_address, but it never names those siblings or says so explicitly, so differentiation is left to inference.

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?

Usage is only implied by the phrase 'emitted by a specific transaction' — an agent can infer this is the tool for transaction-scoped event lookup. There is no explicit when-to-use/when-not guidance and no mention of the alternative lookup routes (block, contract address) that share this family.

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