Skip to main content
Glama

Transaction status

get_transaction
Read-only

Status of a transaction by hash, with a vault swap decoded (what was sold and bought).

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
hashYesTransaction hash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that a vault swap is decoded into sold/bought legs, which is behavioral context beyond the annotations, but it says nothing about pending vs confirmed transactions, non-swap transactions, or what happens when the hash is unknown.

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

Conciseness5/5

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

One sentence, front-loaded with the core operation (status lookup by hash) and followed by the decoding detail. Nothing is redundant or padded.

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?

For a simple one-parameter read tool with no output schema, the description covers what is returned at a high level. It stops short of describing status states, failure/not-found behavior, or whether the swap decode is conditional, which an agent would need when interpreting results.

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 the single hash parameter is fully documented with a 64-hex pattern, so the schema carries the specification. The description's 'by hash' restates rather than enriches that, and adds no format or validity hints.

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 names the resource (a transaction), the lookup key (hash), and the added value (decoded vault swap showing what was sold and bought). That is enough to distinguish it from submit_transaction or get_vault, though it phrases the action as a noun ('Status of a transaction') rather than a verb.

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?

No when-to-use guidance is given: it does not say to call this after submit_transaction to poll for inclusion, nor how it relates to quote or build_swap. There are no exclusions or prerequisites, leaving the agent to infer usage from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.