Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_token_supply

Retrieve the total supply of an SPL Token by providing the mint public key on the Solana blockchain using the MCP server's tools.

Instructions

Returns the total supply of an SPL Token type.

Args: mint (str): Public key of token mint

Returns: str: Token supply information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYes

Implementation Reference

  • The handler function for the 'get_token_supply' tool. It is registered via the @mcp.tool() decorator and implements the logic to retrieve the total supply of an SPL token using the Solana RPC AsyncClient.
    @mcp.tool()
    async def get_token_supply(mint: str) -> str:
        """Returns the total supply of an SPL Token type.
    
        Args:
            mint (str): Public key of token mint
    
        Returns:
            str: Token supply information
        """
        async with AsyncClient(rpc_url) as client:
            supply = await client.get_token_supply(Pubkey.from_string(mint))
            return f"Token supply: {supply}"
  • src/server.py:607-607 (registration)
    The @mcp.tool() decorator registers the get_token_supply function as an MCP tool.
    @mcp.tool()
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 token supply information, but lacks details on permissions, rate limits, error conditions, or whether it's a read-only operation. This is a significant gap 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 and front-loaded, with the main purpose stated first followed by parameter and return details. It avoids unnecessary verbosity, though the structure could be slightly improved by integrating the parameter explanation more seamlessly.

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) and lack of annotations or output schema, the description is minimally adequate. It covers the basic purpose and parameter semantics but lacks behavioral context and usage guidelines, which are important for effective tool invocation by an AI agent.

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 adds meaning by explaining that the 'mint' parameter is the 'Public key of token mint', which clarifies its purpose beyond the schema's generic 'Mint' title. However, with 0% schema description coverage and only one parameter, the description compensates adequately but does not provide extensive details like format examples or constraints.

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 ('Returns') and resource ('total supply of an SPL Token type'), making it easy to understand what the tool does. However, it does not explicitly differentiate from sibling tools like 'get_supply' or 'get_token_account_balance', which might handle related but different queries.

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_supply' and 'get_token_account_balance' present, there is no indication of the specific context or scenarios where this tool is preferred, leaving the agent to infer usage.

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