sui-mcp-server

sui_get_checkpoint

Fetch a Sui checkpoint by sequence number, digest, or the latest to obtain its header, summary, and digest with automatic routing between live and archive nodes.

Instructions

Fetch a checkpoint by sequence number, digest, or 'latest'. Returns the checkpoint header, summary (timestamp, networkTotalTransactions), and digest. Defaults to 'auto' routing — live first, archive fallback. For latest=true the live node is always authoritative; auto still works (archive returns its latest as a fallback if live is unreachable).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sui_get_checkpoint"
  }
}

Input Schema

Name	Required	Description
`sequence_number`	No	Checkpoint sequence number as a string. Mutually exclusive with `digest` and `latest`.
`digest`	No	Base58 checkpoint digest. Mutually exclusive with the others.
`latest`	No	Set true to fetch the latest checkpoint.
`source`	No	Routing policy. 'auto' (default) tries live then archive. 'live' / 'archive' force a single endpoint.
`network`	No	Sui network. Defaults to the server's configured default (usually mainnet).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description bears full burden. It discloses routing policy, fallback to archive, and authoritative behavior for latest. It does not mention error conditions or permissions, but the core behavioral traits are covered.

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?

Two sentences, front-loaded with purpose, then routing details. No redundant information. Every sentence adds value.

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?

No output schema, but description lists return fields (header, summary, digest). Enough for an agent to understand what it gets. Could add pagination or error info, but sufficient for typical use.

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% (all 5 params have descriptions), so baseline is 3. The description adds extra meaning: explains 'auto' routing behavior and latest authoritative details, going beyond schema enums.

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 action ('fetch'), resource ('checkpoint'), and identifiers ('sequence number, digest, or latest'). It differentiates from sibling tools like sui_recent_checkpoints and sui_chain_tip by specifying distinct query methods.

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 explains routing behavior ('auto' vs 'live' vs 'archive') and authoritative handling for latest. It implicitly guides when to use each source, but does not explicitly state when_not to use this tool compared to alternatives.

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