Skip to main content
Glama
Sign In
sui-mcp-server

sui-mcp-server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

dry_run_transaction

Simulate a transaction to preview effects without executing, enabling safe verification of outcomes before committing.

Instructions

Dry-run a transaction to preview effects without executing.

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": {
      "txBytes": "<txBytes>"
    },
    "name": "dry_run_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
txBytesYesBase64-encoded transaction bytes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It states the tool is non-executing and safe, but lacks details on what exactly is returned (e.g., effects, gas estimates) or any side effects. Adequate but could be richer.

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?

The description is a single sentence that immediately conveys the tool's purpose and outcome. No filler words, front-loaded with the verb 'Dry-run'. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description is somewhat complete but lacks details about the return value (e.g., previewed effects). Since no output schema exists, the description should explain what the output contains, which it does not.

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% for the single parameter 'txBytes', which is described as 'Base64-encoded transaction bytes'. The description adds no additional meaning beyond the schema, so baseline score of 3 applies.

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 clearly states the tool performs a 'dry-run' on a transaction to 'preview effects without executing', which is a specific verb-resource combination. It distinguishes itself from execution tools like 'move_call' and inspection tools like 'dev_inspect'.

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?

The description provides clear guidance: use to preview effects without executing. However, it does not explicitly exclude alternative tools (e.g., 'dev_inspect' is a sibling with similar functionality) or state when not to use this tool.

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

Deploy Server

Other Tools