Skip to main content
Glama

Trace a transaction (EVM and Canton)

zenith_get_transaction
Read-only

Fetch a transaction's status, fee, decoded calls and events, and the Canton update that settled it, or learn why it was never mined via the pending-transaction index.

Instructions

Status, fee, decoded call and events (verified ABIs, ERC-20 and the Gateway's own events), whether it was a Gateway deposit, and the Canton update that settled it: update ID, command ID, settlement time. If it was never mined, explains why using Gateway's pending-transaction index.

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": {
      "hash": "<hash>"
    },
    "name": "zenith_get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash (0x + 64 hex)
includeCantonLinkNoLook up the Canton update in the explorer index (a few extra requests)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: it explains pending transactions return a reason via the Gateway pending index, discloses the Canton lookup as an additional cost, and states the verification source of decoded data (verified ABIs, ERC-20 and Gateway events). It does not cover failure modes or error behavior.

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?

Dense but purposeful: nearly every clause names a distinct returned field, and the pending-transaction behavior is placed at the end where it reads naturally. The opening field list is slightly front-loaded as a noun phrase rather than an action statement, but there is little wasted wording.

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?

With no output schema, the description carries the burden of describing returns and does so field by field, including the Canton settlement data and the not-mined case. For a read-only lookup with two well-documented parameters, this is nearly sufficient; only error/edge behaviors and multi-chain applicability remain unstated.

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%, so both parameters and the includeCantonLink cost note are already documented in the schema. The description's mention of the Canton update loosely ties to that flag but adds no format, hash-chain, or defaulting details beyond the schema; baseline 3 is appropriate.

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?

The description names a specific resource (a transaction) and enumerates exactly what it returns: status, fee, decoded call, events with verified ABIs, Gateway deposit flag, and the settling Canton update. It clearly differentiates itself from siblings like zenith_get_logs or zenith_get_account by emphasizing cross-chain settlement (EVM plus Canton) and decoded call data.

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: an agent can infer this is the tool for inspecting one transaction hash, and the 'never mined' sentence hints it also handles pending hashes. However, no explicit when-to-use/when-not-to-use guidance or named alternatives are given, so routing decisions are left to inference.

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