sui-mcp-server

sui_recent_checkpoints

Retrieve recent checkpoints with digests, timestamps, and transaction counts to monitor Sui blockchain activity.

Instructions

Recent checkpoint feed with digests, timestamps, and per-checkpoint transaction counts.

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_recent_checkpoints"
  }
}

Input Schema

Name	Required	Description	Default
`last`	No
`network`	No	Sui network. Defaults to the server's configured default.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided. The description mentions the output includes digests, timestamps, and transaction counts, but does not disclose ordering, default recency, or pagination behavior. Some behavioral context is given but incomplete.

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 of 10 words, front-loaded with the core purpose. No unnecessary words or repetitions.

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 simple tool with two optional parameters and no output schema, the description covers the main output fields and purpose. Lacks details on default behavior (e.g., how many checkpoints by default) but is generally sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (only 'network' has a description). The description does not explain the 'last' parameter, which controls the number of checkpoints returned. It adds minimal semantic value beyond 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?

The description clearly states the tool provides a feed of recent checkpoints with digests, timestamps, and transaction counts. It distinguishes from siblings like sui_get_checkpoint (single checkpoint) and sui_stream_checkpoints (streaming).

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., sui_get_checkpoint for a single checkpoint, sui_stream_checkpoints for streaming). The description does not mention prerequisites or exclusions.

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