Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

get_transaction_status

Read-onlyIdempotent

Check a Base transaction's status and outcome—pending, succeeded, reverted, or not found—including block confirmations, fee paid, net token movements, and decoded revert reason.

Instructions

Reports what a sent Base transaction did: pending, succeeded, reverted or not found; its block and confirmations; the fee paid; the net token movements for the sender (GBLIN shares minted or redeemed, USDC, basket tokens); and, when it reverted, the decoded reason.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesThe transaction hash.

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
hashYes
noteNo
blockNo
revertNo
statusYes
fee_ethNo
explorerNo
gas_usedNo
gas_limitNo
confirmationsNo
balance_changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.5

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior is covered. The description adds meaningful behavioral context beyond annotations: pending/succeeded/reverted/not found outcomes, block and confirmation reporting, fee paid, token movements, and decoded revert reasons. It does not discuss operational limits such as caching or rate limits, but it substantially improves transparency.

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?

The description is a single front-loaded sentence that immediately states what the tool reports, followed by a tightly packed list of relevant outcomes. Every clause maps to useful behavior or return information, with no filler.

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?

Given the output schema, annotations, and fully documented input parameter, the description is complete enough for an agent to understand the tool's purpose and call it correctly. It covers status categories, failure reasons, and token movement reporting, leaving no critical gap for this read-only lookup tool.

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?

There is one required parameter with 100% schema description coverage, and the schema documents the hash format and pattern. The description says the tool reports on a transaction but does not add hash-specific semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 a specific verb and resource: it reports what a sent Base transaction did. It also enumerates the outcomes and returned data, making the tool's purpose clear. It does not explicitly distinguish itself from the sibling get_receipt tool, so it falls short of a 5.

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 phrase 'sent Base transaction' implies a post-send status check, and the listed statuses clarify the expected context. However, there is no explicit guidance on when to use this tool versus alternatives such as get_receipt, and no exclusions are stated.

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