Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_block_time

Retrieve the estimated production time of a specific block on the Solana blockchain by providing its slot number. Returns the block time in a clear, formatted string.

Instructions

Fetch the estimated production time of a block.

Args: slot (int): Block slot number

Returns: str: Block time in the format "Block time: {time}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYes

Implementation Reference

  • The handler function for the 'get_block_time' tool. It uses AsyncClient to fetch the block time for a given slot from the Solana RPC and formats the response as a string. The @mcp.tool() decorator registers it as an MCP tool.
    @mcp.tool()
    async def get_block_time(slot: int) -> str:
        """Fetch the estimated production time of a block.
    
        Args:
            slot (int): Block slot number
    
        Returns:
            str: Block time in the format "Block time: {time}"
        """
        async with AsyncClient(rpc_url) as client:
            time = await client.get_block_time(slot)
            return f"Block time: {time}"
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 mentions 'estimated production time' and the return format, but doesn't cover critical aspects like whether this is a read-only operation, potential errors, rate limits, or network dependencies. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 well-structured and appropriately sized, with a clear purpose statement followed by parameter and return details in separate sections. Every sentence adds value, and there is no unnecessary information, making it efficient and easy to parse.

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's low complexity (one parameter, no output schema, no annotations), the description is reasonably complete for basic usage. It explains what the tool does, the parameter, and the return format. However, it lacks context on behavioral traits and usage guidelines, which could be important for an agent in a server with many similar tools.

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 includes an 'Args' section that documents the 'slot' parameter as a 'Block slot number', adding meaning beyond the schema's minimal coverage (0%). However, with only one parameter and the schema providing no descriptions, the description compensates adequately but doesn't fully detail constraints or examples, keeping it at a baseline level.

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 with a specific verb ('Fetch') and resource ('estimated production time of a block'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_block' or 'get_block_height', which might also retrieve block-related information, so it doesn't reach the highest 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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools related to blocks (e.g., get_block, get_block_height, get_blocks), there is no indication of specific use cases, prerequisites, or exclusions, leaving the agent to infer usage from the 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