Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

get_largest_accounts

Retrieve the 20 largest Solana accounts by lamport balance using the Model Context Protocol Server for Solana Client. Access essential blockchain data for analysis or monitoring.

Instructions

Returns the 20 largest accounts, by lamport balance.

Returns: str: Largest accounts info in the format "Largest accounts: {accounts}"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_largest_accounts' tool. It uses the Solana AsyncClient to fetch the 20 largest accounts by lamport balance from the mainnet-beta RPC and formats the result as a string.
    @mcp.tool()
    async def get_largest_accounts() -> str:
        """Returns the 20 largest accounts, by lamport balance.
    
        Returns:
            str: Largest accounts info in the format "Largest accounts: {accounts}"
        """
        async with AsyncClient(rpc_url) as client:
            accounts = await client.get_largest_accounts()
            return f"Largest accounts: {accounts}"
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. It mentions the return format ('str: Largest accounts info in the format "Largest accounts: {accounts}"'), which adds some behavioral context. However, it lacks details on permissions, rate limits, network effects, or error conditions, which are important for a read operation in a blockchain context.

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: the first sentence states the core purpose, and the second clarifies the return format. There's no wasted text, though the formatting of the return statement could be slightly cleaner (e.g., avoiding nested quotes).

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 minimally adequate. It explains what the tool does and the return format, but for a blockchain tool with many siblings, more context on usage or limitations would improve completeness. The lack of annotations means the description should do more to compensate.

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%. The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. It correctly avoids unnecessary parameter details, focusing on the tool's output instead.

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 20 largest accounts, by lamport balance.' It specifies the verb ('Returns'), resource ('largest accounts'), and scope ('20 largest, by lamport balance'). However, it doesn't explicitly differentiate from sibling tools like 'get_token_largest_accounts' or 'get_account_info', 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 (e.g., 'get_account_info', 'get_token_largest_accounts'), there's no indication of context, prerequisites, or exclusions. The agent must infer usage from the purpose alone.

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