Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_supply

Retrieve current supply data from the Solana blockchain using the Model Context Protocol Server, providing essential details in a clear and structured format.

Instructions

Returns information about the current supply.

Returns: str: Supply information in the format "Supply info: {supply}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • This is the handler function for the 'get_supply' tool. It is decorated with @mcp.tool(), which registers it as an MCP tool. The function fetches the current supply information from the Solana RPC client and formats it as a string.
    @mcp.tool()
    async def get_supply() -> str:
        """Returns information about the current supply.
    
        Returns:
            str: Supply information in the format "Supply info: {supply}"
        """
        async with AsyncClient(rpc_url) as client:
            supply = await client.get_supply()
            return f"Supply info: {supply}"
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 supply information in a specific string format, which is helpful. However, it lacks details on potential side effects, error conditions, rate limits, or authentication needs. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise and well-structured: it states the purpose in one sentence and the return format in another. Every sentence adds value—the first explains what the tool does, and the second clarifies the output format. There's no wasted text or redundancy.

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 output schema, no annotations), the description is adequate but has clear gaps. It explains the purpose and return format, which is sufficient for basic use. However, without annotations or output schema, it lacks details on error handling, side effects, or how it differs from similar tools like 'get_token_supply', reducing completeness for an agent.

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% (though empty). The description doesn't need to explain parameters, so it meets baseline expectations. No additional parameter semantics are required, but it doesn't go beyond the schema (which is fine given no parameters).

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 supply.' This specifies the verb ('returns') and resource ('current supply'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_token_supply' or other supply-related tools, 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 many sibling tools available (e.g., 'get_token_supply', 'get_balance'), there's no indication of context, prerequisites, or exclusions. The agent must infer usage from the tool name alone, which is insufficient for optimal selection.

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