Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_minimum_ledger_slot

Retrieve the lowest ledger slot recorded by a Solana node, providing essential blockchain synchronization and data integrity insights for the Model Context Protocol Server.

Instructions

Returns the lowest slot that the node has information about in its ledger.

Returns: str: Minimum ledger slot information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_minimum_ledger_slot' tool. It uses an AsyncClient to connect to the Solana RPC endpoint and calls client.get_minimum_ledger_slot() to fetch the lowest slot in the ledger, then formats and returns the result as a string.
    async def get_minimum_ledger_slot() -> str:
        """Returns the lowest slot that the node has information about in its ledger.
    
        Returns:
            str: Minimum ledger slot information
        """
        async with AsyncClient(rpc_url) as client:
            slot = await client.get_minimum_ledger_slot()
            return f"Minimum ledger slot: {slot}"
  • src/server.py:514-514 (registration)
    The @mcp.tool() decorator registers the get_minimum_ledger_slot function as an MCP tool.
    @mcp.tool()
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. It states the tool returns a string with minimum ledger slot information, but does not disclose behavioral traits like potential errors, performance characteristics, or whether the data is cached or real-time. This leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with the first sentence clearly stating the purpose. The second sentence specifies the return type, which is useful. However, the formatting with 'Returns:' could be slightly more integrated, but overall it is efficient with minimal waste.

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?

Given the tool has no parameters and no output schema, the description provides basic purpose and return type. However, it lacks details on behavioral aspects and usage context, which are important for a tool in a complex environment like blockchain ledger queries. This makes it adequate but with clear gaps.

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?

The tool has 0 parameters, and the schema description coverage is 100%. With no parameters to document, the description does not need to add parameter semantics. A baseline of 4 is appropriate as it avoids redundancy and focuses on the tool's purpose.

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 tool's purpose: 'Returns the lowest slot that the node has information about in its ledger.' It specifies the verb ('returns') and resource ('lowest slot'), but does not explicitly differentiate from siblings like 'get_slot' or 'get_first_available_block', which reduces it from a 5.

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. It lacks context about scenarios where knowing the minimum ledger slot is useful compared to other slot-related tools in the sibling list, such as 'get_slot' or 'get_first_available_block'.

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

Related 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/tywenk/mcp-sol'

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