sui-mcp-server

get_checkpoint

Retrieve detailed Sui checkpoint data by providing a sequence number. Access comprehensive information about any checkpoint on the Sui blockchain.

Instructions

Get detailed checkpoint data by sequence number.

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": {
      "sequenceNumber": "<sequenceNumber>"
    },
    "name": "get_checkpoint"
  }
}

Input Schema

Name	Required	Description	Default
`sequenceNumber`	Yes	Checkpoint sequence number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.3May 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It neither confirms that the operation is read-only nor addresses potential issues like response size, rate limits, or data freshness. The term 'detailed' is vague and unhelpful without elaboration.

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, well-structured sentence that conveys the core purpose without any unnecessary words. It is appropriately concise for a tool with one parameter.

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?

Given the lack of output schema and annotations, the description is insufficiently complete. It omits expected return format, whether the operation is safe, and any edge cases. The presence of siblings like 'get_latest_checkpoint' suggests a need for clearer differentiation.

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?

The input schema already provides a description for the single parameter 'sequenceNumber' (100% coverage), so the description adds no additional meaning beyond what the schema states. Baseline score 3 is appropriate.

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 verb 'Get', the resource 'detailed checkpoint data', and the method 'by sequence number'. It effectively distinguishes this tool from siblings like 'get_latest_checkpoint' by specifying how data is retrieved.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_latest_checkpoint'. There is no mention of prerequisites or scenarios where this tool is appropriate, leaving the agent without decision-making context.

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

Deploy Server