Skip to main content
Glama
Sign In

POAScan

by io.github.jakegallen
OverviewDiscussionsAdmin

Transaction

get_transaction
Read-onlyIdempotent

One transaction by its 64-hex id: type, sender, recipient, amount, memo, epoch, timestamp, attestations and finality. Use it to explain a specific tx. Indexed copies first; a tx not yet indexed is fetched once from the network and cached. source (cache, index, node or archive), source_label and as_of say which copy and when it was read. slot_latch: pinned (the fixed winner of a nonce slot in /api/params slot_latch_overrides) or superseded (a twin on that slot, not counted), else null. For an answer's grading outcome use get_answer_receipt.

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

Input Schema

NameRequiredDescriptionDefault
hashYes64-character hex transaction id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hash / description
      Added value: +"64-character hex transaction id"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: indexed copies are preferred, unindexed transactions are fetched once from the network and cached, and source/source_label/as_of describe which copy was read and when. It also explains slot_latch pinned/superseded semantics and finality-related fields.

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?

The key scope is front-loaded and most sentences carry useful behavioral detail. It is dense and slightly packed, but there is little obvious waste for a tool whose result fields need explanation.

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

Completeness5/5

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

With one required parameter and no output schema, the description supplies the missing return-shape context: transaction fields, source provenance, as_of timing, and slot_latch meaning. It also explicitly points to the sibling for grading outcomes.

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?

The schema already fully documents the single hash parameter with a 64-character hex pattern. The description repeats that it is a 64-hex id but does not add format or lookup details beyond the schema.

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?

States a specific verb/resource: retrieve one transaction by its 64-hex id, and enumerates the returned transaction details. It is clearly distinguishable from list_transactions and from get_answer_receipt.

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

Usage Guidelines5/5

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

Explicitly says to use it to explain a specific transaction and names get_answer_receipt as the alternative for grading outcomes. This gives clear when-to-use guidance and routes away from a sibling when appropriate.

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

All POAScan toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources