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

sui-mcp-server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_transaction

Retrieve detailed information about a Sui transaction using its digest. Optionally include input, effects, and events.

Instructions

Get transaction details by digest.

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": {
      "digest": "<digest>"
    },
    "name": "get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
digestYesTransaction digest
showInputNoShow transaction input (default: true)
showEffectsNoShow effects (default: true)
showEventsNoShow events (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided; description only states purpose. Does not disclose behavioral traits like read-only nature, side effects, or performance implications. Minimal beyond purpose.

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?

Single sentence with no fluff. Efficiently states purpose and method.

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

Completeness2/5

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

No output schema; description omits details like what the response contains or how optional booleans (showInput, showEffects, showEvents) affect results. Incomplete for an agent to understand full behavior.

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 100%, so the schema already explains parameters. Description adds no extra meaning beyond what schema provides. 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?

Description clearly states it retrieves transaction details by digest, using a specific verb and resource. It distinguishes from siblings like query_transactions that handle multiple transactions.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., query_transactions for listings). No mention of prerequisites or context.

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