Skip to main content
Glama

Blazar Polygon plugin

Gas: fees, action costs, tx estimate (Polygon, Base, Ethereum)

blazar_gas
Read-onlyIdempotent

Current gas on Polygon (default), Base or Ethereum (chain param): base fee, priority fee, maxFeePerGas and native/USD, plus the cost in native coin and USD of common actions (approve, swap, aggregator swap; on Polygon also stake, claim, staking v2 exit). Optionally estimate one tx (from, to, data, value). Use before small trades: gas can exceed a small trade's value (often on Ethereum).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blazar_gas"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional: target of a tx to estimate.
dataNoOptional calldata.
fromNoOptional: sender of a tx to estimate.
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.
valueNoOptional wei value.

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
polUsdNo
chainIdNo
typicalNo
nativeUsdNo
baseFeeGweiNo
blockNumberNo
transactionNo
gasPriceGweiNo
nativeSymbolNo
priorityFeeGweiNo
maxFeePerGasGweiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real content beyond that: which fee fields are returned, which action costs are priced per chain, and that the tx estimate is optional. It omits operational traits such as freshness/caching of gas figures and any rate limits, which matters for a live-fee tool.

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 resource and default chain, then the returned fields, then the optional estimation mode, then the usage trigger. Dense but every clause carries information. The parenthetical action list is slightly crowded but not wasteful.

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-shape explanation is not strictly required, yet the description's enumeration of fee fields and action costs usefully frames what the agent will get. Chain coverage and the optional estimation path are both addressed. Minor gap: no statement on how the estimation mode relates to the dedicated simulation/decode siblings.

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 100%, including the chain enum with chain IDs and the Polygon-only note for BZB tools, so the schema already carries the parameter meaning. The description only reinforces that chain defaults to Polygon and that from/to/data/value together form a single optional estimation request. Baseline 3 is appropriate; no syntax or format detail is added beyond the schema.

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+resource: current gas fees (base fee, priority fee, maxFeePerGas) on three named chains, plus per-action cost breakdowns, plus an optional single-tx estimate. It also scopes the action list by chain (Polygon-only stake/claim/exit), which makes the resource boundary concrete. It does not name a sibling, so the overlap with blazar_simulate_tx for the estimation path is left for the agent to infer.

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 a clear triggering condition: use before small trades because gas can exceed a small trade's value, especially on Ethereum. That is actionable context rather than a restatement. It stops short of explicit exclusions, e.g. it does not say to use blazar_simulate_tx instead when the goal is a full execution simulation rather than a fee figure.

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