Skip to main content
Glama

helius_get_token_largest_accounts

Retrieve the largest token accounts for a specific Solana token mint to analyze distribution and identify major holders.

Instructions

Get the largest token accounts for a specific token mint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenAddressYes
commitmentNo

Implementation Reference

  • The main handler function implementing the tool logic. Validates the token mint address and fetches the largest token accounts using the Helius RPC connection.
    export const getTokenLargestAccountsHandler = async (input: GetTokenLargestAccountsInput): Promise<ToolResultSchema> => {
      const tokenAddressResult = validatePublicKey(input.tokenAddress);
      if (!(tokenAddressResult instanceof PublicKey)) {
        return tokenAddressResult;
      }
      try {
        const largestAccounts = await (helius as any as Helius).connection.getTokenLargestAccounts(tokenAddressResult, input.commitment);
        return createSuccessResponse(`Token largest accounts: ${JSON.stringify(largestAccounts.value)}`);
      } catch (error) {
        return createErrorResponse(`Error getting token largest accounts: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The input schema definition for the tool, specifying parameters tokenAddress (required) and optional commitment.
    {
      name: "helius_get_token_largest_accounts",
      description: "Get the largest token accounts for a specific token mint",
      inputSchema: {
        type: "object",
        properties: {
          tokenAddress: { type: "string" },
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: ["tokenAddress"]
      }
  • src/tools.ts:554-554 (registration)
    The tool registration mapping the name to its handler function in the handlers dictionary.
    "helius_get_token_largest_accounts": getTokenLargestAccountsHandler,
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical behavioral details: it doesn't specify what 'largest' means (e.g., by balance, count), whether results are paginated, rate limits, authentication requirements, or error handling. For a read operation with zero annotation coverage, this leaves significant 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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by directly conveying the tool's function, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 0% schema description coverage for a tool with 2 parameters, the description is incomplete. It lacks details on return values (e.g., account list format, data included), behavioral constraints, and parameter semantics, leaving the agent with insufficient context for reliable use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It mentions 'token mint' which relates to 'tokenAddress', but doesn't explain parameter meanings, formats, or the purpose of 'commitment' (despite its enum values). With 2 parameters and no schema descriptions, this is inadequate.

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 action ('Get') and resource ('largest token accounts for a specific token mint'), making the purpose immediately understandable. It distinguishes from siblings like 'helius_get_token_accounts' by specifying 'largest' accounts rather than all accounts, though it doesn't explicitly contrast with all relevant alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like 'helius_get_token_accounts' or 'helius_get_token_accounts_by_owner'. The description implies usage for token mint analysis but offers no context about prerequisites, limitations, or comparison to sibling tools.

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

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/dcSpark/mcp-server-helius'

If you have feedback or need assistance with the MCP directory API, please join our Discord server