Skip to main content
Glama
Sign In
Model Context Protocol Server for Solana Client

Model Context Protocol Server for Solana Client

by tywenk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_inflation_governor

Retrieve the current inflation governor information from the Solana blockchain using the specified RPC method to monitor or analyze monetary policy settings.

Instructions

Returns the current inflation governor.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_inflation_governor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.py:165-174 (handler)
    The tool handler function decorated with @mcp.tool(), implementing the get_inflation_governor tool by querying the Solana RPC client and returning the formatted inflation governor information.
    @mcp.tool()
async def get_inflation_governor() -> str:
    """Returns the current inflation governor.

    Returns:
        str: Inflation governor info in the format "Inflation governor: {governor}"
    """
    async with AsyncClient(rpc_url) as client:
        governor = await client.get_inflation_governor()
        return f"Inflation governor: {governor}"
  • src/server.py:165-165 (registration)
    The @mcp.tool() decorator registers the get_inflation_governor function as an MCP tool.
    @mcp.tool()

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removed
  2. First observed

TDQS

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 full burden. It only states what the tool returns, without mentioning behavioral aspects like whether it's a read-only operation, potential rate limits, authentication requirements, or how current 'current' actually is (real-time vs cached). This leaves significant gaps for a tool with no 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 appropriately sized with two sentences: one stating the purpose and one describing the return format. It's front-loaded with the core functionality first. The return format description could potentially be more concise, but overall it's efficient.

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?

For a zero-parameter read operation with no output schema, the description covers the basic purpose and return format. However, it lacks important context about what an 'inflation governor' actually represents in this system, and with no annotations, it should provide more behavioral transparency about the operation's characteristics.

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 with 100% schema description coverage, so the baseline is 4. The description correctly indicates no parameters are needed by not mentioning any, which aligns perfectly with the empty input 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 current inflation governor.' This is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_inflation_rate' or 'get_inflation_reward', which prevents 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 sibling tools like 'get_inflation_rate' and 'get_inflation_reward' available, there's no indication of when this specific inflation-related query is appropriate versus those other options.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

Related Tools