gblin-treasury-risk-regime

actions.preview

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`from`	Yes	The wallet that will send the steps.
`steps`	Yes	The steps, in order: target and calldata (or their send_calls spellings, to and data), value in wei (optional), gas (optional).

Output Schema

TableJSON Schema

Name	Required	Description
`from`	No
`note`	No
`block`	No	The block the simulation ran on.
`steps`	Yes	Per step: success, gas used, whether the given limit is enough, recommended limit, revert reason.
`would_succeed`	Yes	True only if every step succeeds in the simulation.
`balance_changes`	Yes	Net token and ETH movements for the wallet.
`first_failing_step`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 30, 2026

changedInput schema / properties / steps / description

Previous value: -"The steps, in order: target, calldata, value in wei (optional), gas (optional)."New value: +"The steps, in order: target and calldata (or their send_calls spellings, to and data), value in wei (optional), gas (optional)."

addedInput schema / properties / steps / items / properties / calldata / description
```
Added value: +"ABI-encoded call. Alias: data."
```

addedInput schema / properties / steps / items / properties / data

Added value: +{
+  "pattern": "^0x([0-9a-fA-F]{2})*$",
+  "type": "string"
+}

addedInput schema / properties / steps / items / properties / target / description
```
Added value: +"Contract to call. Alias: to."
```

addedInput schema / properties / steps / items / properties / to

Added value: +{
+  "pattern": "^0x[a-fA-F0-9]{40}$",
+  "type": "string"
+}

changedInput schema / properties / steps / items / required

Previous value: -[
-  "target",
-  "calldata"
-]New value: +[]

AddedSep 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real context beyond them: each step sees prior state, the preview is 'evidence, not a guarantee' because state can change before landing, and it reports per-step success, gas, gas-limit sufficiency, and decoded revert reasons. It omits the 8-step cap and any rate/latency behavior, so not a 5.

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?

One dense, front-loaded paragraph with no filler; the state-chaining and caveat sentences are the most valuable. The enumeration of per-step return fields is somewhat redundant given an output schema exists, which keeps it from a 5.

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?

For a simulation tool with annotations and an output schema, the description covers the crucial non-structured facts: sequential state visibility, alias spellings, and the non-guarantee caveat. The only notable omission is the maxItems: 8 limit on steps, which an agent should know before composing a batch.

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%, so the schema already documents from, steps, and the to/target and data/calldata aliases. The description restates the aliases and notes value and gas are optional but adds no format or semantic detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

The description gives a precise verb and resource ('Simulates a list of transactions in sequence against the latest Base block') plus the key scoping qualifier 'before anything is signed', which separates it from actions.prepare. An agent can identify the operation and its pre-signing role without opening the 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?

It clearly states the context of use: run the sequence as if the wallet sent them, before signing, so dependent steps (approval before mint) can be validated. It does not name an explicit alternative such as actions.prepare or state when not to use it, so it stops short of full when/when-not guidance.

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

All gblin-treasury-risk-regime tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.