Skip to main content
Glama

Blazar Polygon plugin

Tx status, receipt, decoded logs, revert reason

blazar_tx_status
Read-onlyIdempotent

Did a tx land on Polygon (default), Base or Ethereum (chain param; the hash only exists on the chain it was sent to)? Given a hash: not_found / pending / confirmed / reverted, block and confirmations, gas fee, decoded logs (ERC-20 Transfer/Approval, fee-router swaps, staking, pair Swap/Sync), per-token balance changes, decoded calldata for BlazarForce contracts, and the revert reason (replayed). Pass from to also get latest vs pending nonce. Use after every send, and before ever re-sending: never blind-retry.

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

Input Schema

NameRequiredDescriptionDefault
fromNoOptional sender: adds latest vs pending nonce (useful when the hash is unknown).
hashYesTransaction hash.
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.

Output Schema

NameRequiredDescriptionDefault
toNo
docsNo
fromNo
hashNo
logsNo
nextNo
noteNo
chainNo
nonceNo
landedNo
revertNo
statusNo
chainIdNo
gasUsedNo
explorerNo
gasFeePolNo
retryableNo
blockNumberNo
transactionNo
gasFeeNativeNo
nativeSymbolNo
retryAfterMsNo
confirmationsNo
tokenBalanceChangesNo
effectiveGasPriceGweiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description need not restate safety. It adds genuinely non-structured behavior: the revert reason is obtained by replay, and the hash only exists on the chain it was sent to, which explains a common failure mode (wrong chain → not_found). It does not mention latency or RPC cost of the replay on a reverted tx.

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?

Front-loaded with the decision question, then the outcome taxonomy, then the return payload, then the operating rule — good ordering with no filler sentences. Parenthetical stacking ("chain param; the hash only exists...") makes it dense to parse in one pass, which keeps it off a 5.

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 an output schema present, the description need not document return values, yet its outcome enumeration and the replay-based revert reason cover the only ambiguity an agent faces (pending vs. not_found on the wrong chain). Annotations handle the safety profile, so nothing material is left unspecified.

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 coverage is 100%, so the baseline is 3, and the description earns above baseline by adding the chain-scoping caveat ("the hash only exists on the chain it was sent to") and by flagging that `from` matters specifically when the hash is unknown. The Polygon-only restriction on BZB/BlazarSwap tools is also useful selection context not present in 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?

The opening question plus "Given a hash: not_found / pending / confirmed / reverted" names a specific verb (look up tx outcome) and resource (transaction by hash), and enumerates the return surface (block/confirmations, gas fee, decoded logs, balance deltas, revert reason). This distinguishes it clearly from blazar_decode_tx (decode-only) and blazar_simulate_tx (pre-execution) without needing to open their schemas.

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

Usage Guidelines4/5

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

Gives explicit lifecycle guidance: "Use after every send, and before ever re-sending: never blind-retry." That is a concrete when-to-use rule with a prohibition. It does not name an alternative tool for the pre-send case (e.g. real sibling blazar_simulate_tx), so routing between competing options is left slightly implicit.

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.

Resources