Skip to main content
Glama
enesjakozh
tywenk

Model Context Protocol Server for Solana Client

by tywenk
OverviewSchemaRelated ServersScoreDiscussions
Python

get_inflation_rate

Retrieve the current inflation rate for the Solana blockchain epoch with precision, aiding in economic analysis and decision-making.

Instructions

Returns the specific inflation values for the current epoch.

Returns: str: Inflation rate info in the format "Inflation rate: {rate}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.py:177-186 (handler)
    The handler function for the 'get_inflation_rate' tool. It is registered via the @mcp.tool() decorator and implements the tool logic by querying the Solana RPC client for the current epoch's inflation rate and returning a formatted string.
    @mcp.tool()
async def get_inflation_rate() -> str:
    """Returns the specific inflation values for the current epoch.

    Returns:
        str: Inflation rate info in the format "Inflation rate: {rate}"
    """
    async with AsyncClient(rpc_url) as client:
        rate = await client.get_inflation_rate()
        return f"Inflation rate: {rate}"
  • src/server.py:177-177 (registration)
    The @mcp.tool() decorator registers the get_inflation_rate function as an MCP tool.
    @mcp.tool()
  • src/server.py:178-182 (schema)
    The function signature and docstring define the tool schema: no input parameters, returns a string with inflation rate information.
    async def get_inflation_rate() -> str:
    """Returns the specific inflation values for the current epoch.

    Returns:
        str: Inflation rate info in the format "Inflation rate: {rate}"

Tool Definition Quality

B3.1/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 tool returns inflation values but does not explain what 'current epoch' means, whether this is a read-only operation, potential rate limits, or error conditions. For a tool with zero annotation coverage, this is insufficient, though it minimally describes the return format.

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 main purpose stated first and return format details following. Both sentences earn their place by providing essential information without redundancy, though the return format could be integrated more smoothly.

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, no annotations, and no output schema, the description is moderately complete. It explains what the tool does and the return format, but lacks context on behavior, usage, or differentiation from siblings, leaving gaps for an AI agent to understand full applicability.

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% (as there are no parameters to describe). The description does not need to add parameter semantics, so a baseline score of 4 is appropriate, as it efficiently avoids unnecessary details while matching the schema.

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 specific inflation values for the current epoch.' It specifies the verb ('returns'), resource ('inflation values'), and scope ('current epoch'). However, it does not explicitly differentiate from sibling tools like 'get_inflation_governor' or 'get_inflation_reward', which reduces the score from a perfect 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 any mention of prerequisites, context, or comparisons to sibling tools such as 'get_inflation_governor' or 'get_inflation_reward', leaving the agent without explicit usage instructions.

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