Skip to main content
Glama
enesjakozh
tywenk

Model Context Protocol Server for Solana Client

by tywenk
OverviewSchemaRelated ServersScoreDiscussions
Python

get_epoch_info

Retrieve detailed information about the current epoch on the Solana blockchain using this tool, enabling users to access essential data for blockchain analysis and decision-making.

Instructions

Returns information about the current epoch.

Returns: str: Epoch information in the format "Epoch info: {info}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.py:117-127 (handler)
    The handler function that implements the 'get_epoch_info' tool logic. Decorated with @mcp.tool() which registers it in the MCP server. It queries the Solana RPC client for epoch info and formats the response.
    @mcp.tool()
async def get_epoch_info() -> str:
    """Returns information about the current epoch.

    Returns:
        str: Epoch information in the format "Epoch info: {info}"
    """
    async with AsyncClient(rpc_url) as client:
        info = await client.get_epoch_info()
        return f"Epoch info: {info}"
  • src/server.py:117-117 (registration)
    The @mcp.tool() decorator registers the get_epoch_info function as a tool in the FastMCP server.
    @mcp.tool()

Tool Definition Quality

B3.2/5.0
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 return format ('Epoch information in the format "Epoch info: {info}"'), which adds some context beyond the basic purpose. However, it lacks details on potential errors, rate limits, network dependencies, or what 'current epoch' entails in this context, making it insufficient for a mutation-free but context-sensitive tool.

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 front-loaded with the core purpose in the first sentence, followed by a concise return format specification. Every sentence earns its place without redundancy, making it efficiently structured 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 simplicity (0 parameters, no annotations, no output schema), the description is reasonably complete for a basic read operation. It covers purpose and return format. However, without annotations or output schema, it could benefit from more behavioral context (e.g., what 'epoch' means here, error cases), but it's adequate for minimal complexity.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is appropriate. It slightly exceeds the baseline by including return format info, but since there are no params, a score of 4 reflects that it adequately addresses the minimal requirement.

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 information about the current epoch.' This is a specific verb ('Returns') and resource ('information about the current epoch'), making it understandable. However, it doesn't explicitly differentiate from sibling tools like get_epoch_schedule, which might provide related but different epoch data, so it falls short of 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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like get_epoch_schedule, get_slot, and get_block_height that might offer related temporal or epoch data, there's no indication of context, prerequisites, or exclusions. This leaves the agent without usage direction.

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