Skip to main content
Glama

Blazar Polygon plugin

Decode a tx before signing

blazar_decode_tx
Read-onlyIdempotent

Decode calldata for a tx to a BlazarForce contract or an ERC-20 approve, e.g. one from another tool or agent, so you can check it before signing. Builds already include summaries, so this is for txs from other sources. Polygon only (chain 137).

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": {
      "to": "<to>",
      "data": "<data>"
    },
    "name": "blazar_decode_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
dataYes

Output Schema

NameRequiredDescriptionDefault
argsNo
functionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a real constraint not expressed in the schema: Polygon only (chain 137), which affects whether the call is valid at all. It does not state failure behavior for non-Polygon or unrecognized selectors, but the essential behavioral fact is disclosed.

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?

Three short sentences, front-loaded with the action and its scope, then the usage condition and the chain restriction. Minor redundancy with the title phrase 'before signing' repeated, but nothing extraneous.

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?

An output schema exists, so return-value explanation is not required, and the chain restriction plus source-of-tx condition cover the main decision points. The only gap is error or unsupported-input behavior, which is minor for a read-only decoder.

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 description coverage is 0%, so the description must carry the meaning of `to` and `data`. It does partially: `to` is implied to be a BlazarForce contract or ERC-20 token, and `data` is calldata. It does not clarify expected encoding, whether the target must be a known contract, or how unverified calldata is handled, so compensation for the coverage gap is incomplete.

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?

States a specific verb and resource: decode calldata for a tx targeting a BlazarForce contract or an ERC-20 approve. It also distinguishes itself from the blazar_build_* family by noting builds already include summaries. It stops short of differentiating from the closest sibling, blazar_simulate_tx, which an agent may see as an alternative for pre-signing checks.

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 clear context for use (txs from another tool or agent, to check before signing) and an explicit exclusion (builds already include summaries, so this is for other sources). No guidance on when to prefer simulation over decoding, but the when-to-use condition is unambiguous.

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