Skip to main content
Glama
buildwithgrove

Grove's MCP Server for Pocket Network

get_sui_latest_checkpoint

Retrieve the current checkpoint sequence number for Sui blockchain networks to monitor chain progress and synchronize applications.

Instructions

Get latest checkpoint sequence number

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
networkNoNetwork type (defaults to mainnet)

Implementation Reference

  • Executes the get_sui_latest_checkpoint tool by extracting the network parameter, calling SuiService.getLatestCheckpoint, and formatting the response for the MCP tool.
    case 'get_sui_latest_checkpoint': {
      const network = (args?.network as 'mainnet' | 'testnet') || 'mainnet';
    
      const result = await suiService.getLatestCheckpoint(network);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
        isError: !result.success,
      };
    }
  • Input schema and metadata definition for the get_sui_latest_checkpoint tool, part of the tools array registered via registerSuiHandlers.
    {
      name: 'get_sui_latest_checkpoint',
      description: 'Get latest checkpoint sequence number',
      inputSchema: {
        type: 'object',
        properties: {
          network: {
            type: 'string',
            enum: ['mainnet', 'testnet'],
            description: 'Network type (defaults to mainnet)',
          },
        },
      },
    },
  • Core implementation in SuiService that performs the RPC call to sui_getLatestCheckpointSequenceNumber via the blockchain service.
    async getLatestCheckpoint(
      network: 'mainnet' | 'testnet' = 'mainnet'
    ): Promise<EndpointResponse> {
      const service = this.blockchainService.getServiceByBlockchain('sui', network);
    
      if (!service) {
        return {
          success: false,
          error: `Sui service not found for ${network}`,
        };
      }
    
      return this.blockchainService.callRPCMethod(
        service.id,
        'sui_getLatestCheckpointSequenceNumber',
        []
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get' implies a read operation, the description doesn't mention any behavioral traits like rate limits, authentication requirements, response format, or whether this is a real-time query versus cached data.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple query tool and front-loads the essential information.

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 read operation with one well-documented parameter and no output schema, the description is minimally adequate. However, without annotations or output schema, it should ideally provide more context about what the checkpoint sequence number represents or how it's used in the Sui ecosystem.

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%, with the single parameter 'network' fully documented in the schema including its enum values and default behavior. The description adds no additional parameter information beyond what the schema already provides, meeting the baseline expectation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('latest checkpoint sequence number'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_sui_checkpoint' which presumably retrieves a specific checkpoint rather than the latest one.

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 is provided about when to use this tool versus alternatives. With sibling tools like 'get_sui_checkpoint' available, the description doesn't explain the distinction between getting the latest checkpoint versus a specific one, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/buildwithgrove/mcp-pocket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server