Skip to main content
Glama

Rokha

by ai.rokha
OverviewDiscussionsAdmin

Look up a transaction

singularityagent__transaction
Read-only

Fetch and normalize a transaction, with EVM calldata decoded where the selector is recognized. If no chain is given, searches the chains the hash format allows and reports every chain it was found on. Read finality alongside status, because they answer different questions: status says the chain executed the transaction and it did not revert, while finality says whether the block holding it can still be discarded. final is the only kind that licenses an irreversible decision. reversible means it sits at or near the head and a reorganization would erase it. probabilistic is proof-of-work settlement — it carries a confirmation count and never becomes final at any depth, because the chain offers no point past which reversal is disallowed, only one past which it is expensive; how many confirmations are enough is the caller’s decision. unknown means the endpoint would not say, which is not evidence that it is settled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashYesTransaction hash, txid, or Solana signature.
chainNoChain id, to skip the cross-chain search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties
      Added value: +{
+  "chain": {
+    "description": "Chain id, to skip the cross-chain search.",
+    "type": "string"
+  },
+  "hash": {
+    "description": "Transaction hash, txid, or Solana signature.",
+    "type": "string"
+  }
+}
    • addedInput schema / required
      Added value: +[
+  "hash"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description agrees (fetch/normalize is a read operation – no contradiction). The description adds genuinely useful behavioral context beyond the annotations: a thorough explanation of the `finality` field's four values (final, reversible, probabilistic, unknown) and how they differ from `status`. This interpretive depth is the kind of disclosure an agent needs and is not present in the structured fields.

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 description front-loads the core purpose in the first sentence and arranges information logically (purpose → cross-chain behavior → interpretation guidance). However, the `probabilistic` explanation is drawn-out – the proof-of-work digression about confirmation count being 'the caller's decision' could be tightened. The finality section is the tool's key complexity, so some length is justified, but it runs long enough to dilute attention.

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 explaining return semantics, and it does so thoroughly for the most treacherous field (`finality`), distinguishing four values and their decision implications. It covers the decode behavior and cross-chain reporting. The full return shape isn't enumerated, but the tool's interpretive complexity (finality vs status) is well covered, which is what an agent most needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, giving a baseline of 3. The description adds value beyond the schema: it explains that omitting `chain` triggers a cross-chain search across hash-compatible chains, and it clarifies the `hash` accepts multiple formats. The finality/status explanation effectively documents return semantics implied by the parameters' behavior, going beyond the one-line schema descriptions.

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 title and opening sentence state a specific verb and resource: 'Fetch and normalize a transaction.' The addition of 'with EVM calldata decoded where the selector is recognized' adds meaningful specificity and hints at differentiation from the sibling `decode` tool. It doesn't explicitly name siblings to contrast against, but the cross-chain search and decoding behavior set it apart from `read_contract`, `history`, and `resolve` well enough.

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?

The description gives clear usage context for the `chain` parameter: if omitted, the tool 'searches the chains the hash format allows and reports every chain it was found on.' It also instructs how to interpret results ('Read finality alongside status'). However, it never states when NOT to use this tool or names an alternative to use instead, so it stops short of explicit routing guidance.

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

All Rokha toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources