Skip to main content
Glama
buildwithgrove

Grove's MCP Server for Pocket Network

get_sui_checkpoint

Retrieve checkpoint details by ID or sequence number for Sui blockchain data access through Grove's MCP Server for Pocket Network.

Instructions

Get checkpoint details by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkpointIdYesCheckpoint ID or sequence number
networkNoNetwork type (defaults to mainnet)

Implementation Reference

  • Tool schema definition including name, description, and inputSchema for validating get_sui_checkpoint parameters.
    {
      name: 'get_sui_checkpoint',
      description: 'Get checkpoint details by ID',
      inputSchema: {
        type: 'object',
        properties: {
          checkpointId: {
            type: ['string', 'number'],
            description: 'Checkpoint ID or sequence number',
          },
          network: {
            type: 'string',
            enum: ['mainnet', 'testnet'],
            description: 'Network type (defaults to mainnet)',
          },
        },
        required: ['checkpointId'],
      },
    },
  • Handler logic for the get_sui_checkpoint tool. Extracts parameters, calls SuiService.getCheckpoint, and formats the response.
    case 'get_sui_checkpoint': {
      const checkpointId = args?.checkpointId as string | number;
      const network = (args?.network as 'mainnet' | 'testnet') || 'mainnet';
    
      const result = await suiService.getCheckpoint(checkpointId, network);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
        isError: !result.success,
      };
    }
  • Supporting method in SuiService that performs the RPC call to sui_getCheckpoint via the blockchain service.
    async getCheckpoint(
      checkpointId: string | number,
      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_getCheckpoint', [checkpointId]);
    }
  • src/index.ts:88-101 (registration)
    Registers all tools including Sui tools (via registerSuiHandlers) into the MCP server's tool list.
    const tools: Tool[] = [
      ...registerBlockchainHandlers(server, blockchainService),
      ...registerDomainHandlers(server, domainResolver),
      ...registerTransactionHandlers(server, advancedBlockchain),
      ...registerTokenHandlers(server, advancedBlockchain),
      ...registerMultichainHandlers(server, advancedBlockchain),
      ...registerContractHandlers(server, advancedBlockchain),
      ...registerUtilityHandlers(server, advancedBlockchain),
      ...registerEndpointHandlers(server, endpointManager),
      ...registerSolanaHandlers(server, solanaService),
      ...registerCosmosHandlers(server, cosmosService),
      ...registerSuiHandlers(server, suiService),
      ...registerDocsHandlers(server, docsManager),
    ];
  • src/index.ts:114-127 (registration)
    Routes tool calls to the appropriate handler, including handleSuiTool for Sui tools like get_sui_checkpoint.
    let result =
      (await handleBlockchainTool(name, args, blockchainService)) ||
      (await handleDomainTool(name, args, domainResolver)) ||
      (await handleTransactionTool(name, args, advancedBlockchain)) ||
      (await handleTokenTool(name, args, advancedBlockchain)) ||
      (await handleMultichainTool(name, args, advancedBlockchain)) ||
      (await handleContractTool(name, args, advancedBlockchain)) ||
      (await handleUtilityTool(name, args, advancedBlockchain)) ||
      (await handleEndpointTool(name, args, endpointManager)) ||
      (await handleSolanaTool(name, args, solanaService)) ||
      (await handleCosmosTool(name, args, cosmosService)) ||
      (await handleSuiTool(name, args, suiService)) ||
      (await handleDocsTool(name, args, docsManager));
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'gets' details, implying a read-only operation, but doesn't specify whether it requires authentication, has rate limits, what format the details are returned in, or potential error conditions. This is a significant gap for a tool with no annotation coverage.

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 with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool, making it easy for an agent to parse quickly.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'details' are returned, potential response formats, or error handling. For a tool that likely returns structured blockchain data, this leaves the agent with insufficient context to understand the 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?

The description mentions 'by ID', which aligns with the 'checkpointId' parameter in the schema. However, with 100% schema description coverage, the schema already fully documents both parameters (checkpointId and network). The description adds minimal value beyond what's in the schema, meeting the baseline score for high schema coverage.

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 'Get checkpoint details by ID' clearly states the action (get) and resource (checkpoint details) with a specific identifier requirement. It distinguishes from sibling tools like 'get_sui_latest_checkpoint' by specifying retrieval by ID rather than latest, though it doesn't explicitly mention this distinction.

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 like 'get_sui_latest_checkpoint' or other SUI-related tools. It lacks context about prerequisites, typical use cases, or exclusions, leaving the agent to infer usage from the tool name alone.

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