Skip to main content
Glama

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.

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.

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 readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered; the description adds genuinely non-obvious behavior — POL balance is overridden while token balances stay real, which materially affects how the simulation result should be interpreted. It also discloses the return shape (ok, gas, or error code with hint) absent an output schema. It stops short of describing revert handling or limitations for non-Polygon data.

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?

Three short sentences, front-loaded with purpose, then behavior, then the routing rule. No filler wording; each clause carries distinct information.

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?

Covers purpose, simulation semantics, return values (important with no output schema), and sibling routing for a 4-parameter write-free tool. The remaining gap is that neither the description nor the schema explains the `data` parameter, which the caller must construct correctly.

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%, so the schema documents `to` (omit for contract creation) and `value` (wei, default 0) while `data` and `from` are bare. The description compensates only for `from` by explaining its balance is overridden; it never clarifies that `data` is encoded calldata. That partial compensation supports a baseline 3.

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 actual mechanism (eth_call + estimateGas), so the agent knows exactly what operation happens. It also distinguishes itself from the build_* siblings by noting 'builds already simulate.'

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

Usage Guidelines5/5

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

'Use for txs from other sources; builds already simulate' gives both the when-to-use condition and the when-not-to-use exclusion in one clause. The alternative (build tools) is named by role even without an explicit tool name, leaving little to inference.

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