Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

preview_steps

Read-onlyIdempotent

Simulate sequential transactions against the latest Base block before signing to check success, gas use, gas-limit sufficiency, decoded reverts, and net token/ETH movements.

Instructions

Simulates a list of transactions in sequence against the latest Base block, as if the wallet sent them one after the other, before anything is signed. Each step sees the state the previous ones left (an approval before a mint works). Accepts steps with target or to, calldata or data, and optional value and gas. Returns, per step, whether it would succeed, the gas it uses, whether the gas limit it carries is enough, and the decoded revert reason when it fails; and the net token and ETH movements for the wallet. State can change before transactions land: a successful preview is evidence, not a guarantee.

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>",
      "steps": "<steps>"
    },
    "name": "preview_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesThe wallet that will send the steps.
stepsYesThe steps, in order: target and calldata (or their send_calls spellings, to and data), value in wei (optional), gas (optional).

Output Schema

NameRequiredDescriptionDefault
fromNo
noteNo
blockNoThe block the simulation ran on.
stepsYesPer step: success, gas used, whether the given limit is enough, recommended limit, revert reason.
would_succeedYesTrue only if every step succeeds in the simulation.
balance_changesYesNet token and ETH movements for the wallet.
first_failing_stepNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.5

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag readOnly/idempotent/openWorld, and the description goes well beyond them: it explains the sequential state model, the exact per-step outputs (success, gas used, gas-limit sufficiency, decoded revert reason) plus net token/ETH movement, and warns that chain state can change so a preview is not a guarantee.

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 sentences, front-loaded with the core simulation behavior and followed by input spelling and output shape. Dense but nearly every clause carries information; the parenthetical approval-before-mint example slightly pads an already-clear point.

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?

Even though an output schema exists, the description still summarizes return shape and explicitly flags the non-determinism caveat, which structured fields cannot convey. For a read-only simulation tool with 2 fully documented parameters, nothing needed to invoke or interpret it is missing.

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; the description nonetheless adds the alias contract (target or to, calldata or data), the optionality of value and gas, and that value is denominated in wei. It does not mention the 8-step maximum enforced by 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?

States a specific verb and resource — simulate a sequence of transactions against the latest Base block — plus sequencing semantics ('each step sees the state the previous ones left'). This clearly separates it from sibling write/prepare tools like prepare_action and get_transaction_status.

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?

'before anything is signed' establishes the pre-signing context and the caveat that a successful preview is evidence, not a guarantee. It does not explicitly name which sibling to use instead (e.g. prepare_action for construction, get_transaction_status for post-send), so alternatives are left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.