Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_first_available_block

Retrieve the slot of the lowest confirmed block available on the Solana blockchain using the Model Context Protocol Server for Solana Client.

Instructions

Returns the slot of the lowest confirmed block available.

Returns: str: First available block information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the MCP tool 'get_first_available_block'. Decorated with @mcp.tool() for automatic registration and schema inference from signature and docstring. It creates an AsyncClient to the Solana RPC, calls get_first_available_block(), and returns a formatted string result.
    @mcp.tool()
    async def get_first_available_block() -> str:
        """Returns the slot of the lowest confirmed block available.
    
        Returns:
            str: First available block information
        """
        async with AsyncClient(rpc_url) as client:
            block = await client.get_first_available_block()
            return f"First available block: {block}"
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 the tool returns information but doesn't specify if it's a read-only operation, potential side effects, error conditions, or performance traits like rate limits. The return type hint ('str: First available block information') adds minimal context, but overall, it's insufficient for a tool with zero 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.

Conciseness4/5

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

The description is concise and front-loaded, with the first sentence stating the core purpose clearly. The second sentence adds a return type hint, which is useful but could be integrated more seamlessly. There's no wasted text, making it efficient, though minor structural improvements could enhance readability.

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 0 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on behavioral aspects (e.g., read-only nature, error handling) and doesn't differentiate from siblings. For a simple query tool, this is passable but leaves gaps in usage context.

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 schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately omits parameter information, avoiding redundancy. No additional semantics are required or provided.

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 slot of the lowest confirmed block available.' This specifies the verb ('returns'), resource ('slot'), and scope ('lowest confirmed block available'), making it distinct from siblings like get_block, get_blocks, or get_latest_blockhash. However, it doesn't explicitly differentiate from get_minimum_ledger_slot, which might be similar, keeping it from a perfect score.

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 on when to use this tool versus alternatives. With many sibling tools related to blocks and slots (e.g., get_block, get_blocks, get_minimum_ledger_slot), the description lacks context on use cases, prerequisites, or exclusions, leaving the agent to infer usage based on 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

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