Skip to main content
Glama

Blazar Polygon plugin

Simulate any tx (read-only)

blazar_simulate_tx
Read-onlyIdempotent

Dry-run any Polygon tx with eth_call + estimateGas from from (POL balance overridden, token balances real). Returns ok, gas, or an error code with a hint. Use for txs from other sources; builds already simulate. 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": {
      "from": "<from>",
      "data": "<data>"
    },
    "name": "blazar_simulate_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOmit for contract creation.
dataYes
fromYes
valueNoWei, default 0.

Output Schema

NameRequiredDescriptionDefault
okNo
noteNo
methodNo
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: POL balance is overridden while token balances are real, and failures return an error code with a hint. That is solid added context, though no detail is given on override scope or rate limits.

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?

Four dense clauses, front-loaded with the core action, with the chain restriction and state-override caveat packed in without filler. Every sentence earns its place and the parenthetical carries high-value information compactly.

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 need not be explained, yet the description still flags that failures surface as an error code with a hint. Combined with the chain restriction and the balance-override caveat, an agent has enough to call it correctly; only the meaning of `data` and any RPC dependency are left unstated.

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 50%: `to` and `value` are described in the schema, while `from` and `data` are not. The description does add meaning for `from` by revealing its POL balance is overridden during the call, but `data` (the tx payload) remains unexplained in both places, so this lands at baseline rather than above it.

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?

States a specific verb and resource ("Dry-run any Polygon tx") plus the mechanism (eth_call + estimateGas) and the source of the sender (from `from`). It also distinguishes itself from the build_* family by noting "builds already simulate," so an agent can separate it from blazar_build_any_swap and peers without opening another schema.

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 both a when-to-use ("txs from other sources") and an implicit when-not ("builds already simulate"), which is clear routing guidance. It stops short of naming a specific sibling to use instead or spelling out preconditions such as required RPC availability.

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