Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_get_token_largest_accounts

Retrieve the largest token accounts for any Solana token mint, providing key holder data and balances.

Instructions

Get the largest token accounts for a specific token mint

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "helius_get_token_largest_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenAddressYes
commitmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The description lacks behavioral details such as how 'largest' is defined (e.g., by token balance), any ordering, pagination, or rate limits. With no annotations, the agent has little insight beyond basic functionality.

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 a single sentence, very concise and front-loaded. It conveys the core purpose efficiently, though it could benefit from one more sentence addressing parameter or behavior context.

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 the lack of annotations and output schema, the description is insufficient. It does not explain the response format, what constitutes 'largest', or any filtering criteria. The tool's functionality is under-specified for effective 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 coverage is 0%, so parameters are undocumented in the schema. The description does not explain the meaning of 'tokenAddress' or 'commitment' (the enum values are not described). The agent must infer parameter usage from names alone.

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 verb 'Get' and the resource 'largest token accounts for a specific token mint', making the purpose understandable. However, it does not differentiate from sibling tools like helius_get_token_accounts, which may cause confusion.

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. There is no mention of prerequisites or exclusions.

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