Skip to main content
Glama

helius_get_nft_editions

Retrieve all NFT editions associated with a specific master edition on the Solana blockchain using Helius API data.

Instructions

Get NFT editions for a master edition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
masterEditionIdYes
pageNo
limitNo

Implementation Reference

  • The handler function that executes the logic for helius_get_nft_editions by calling the Helius RPC method getNftEditions.
    export const getNftEditionsHandler = async (input: { masterEditionId: string, page?: number, limit?: number }): Promise<ToolResultSchema> => {
      try {
        const editions = await (helius as any as Helius).rpc.getNftEditions(input);
        return createSuccessResponse(`NFT editions: ${JSON.stringify(editions, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting NFT editions: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The input schema definition for the helius_get_nft_editions tool.
    {
      name: 'helius_get_nft_editions',
      description: 'Get NFT editions for a master edition',
      inputSchema: {
        type: 'object',
        properties: {
          masterEditionId: { type: 'string' },
          page: { type: 'number' },
          limit: { type: 'number' }
        },
        required: ['masterEditionId']
      }
    },
  • src/tools.ts:582-582 (registration)
    The registration mapping the tool name to its handler function.
    "helius_get_nft_editions": helius.getNftEditionsHandler,
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 a read operation ('Get'), which implies non-destructive behavior, but does not mention any traits like rate limits, authentication needs, pagination details (implied by 'page' and 'limit' parameters but not explained), or error handling. This leaves significant gaps in understanding how the tool behaves beyond basic retrieval.

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 directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized, making it easy to parse quickly, though it could benefit from additional details for completeness.

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 complexity of a retrieval tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on parameter semantics, behavioral traits, and expected outputs, making it insufficient for an agent to fully understand and invoke the tool correctly without additional context.

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%, meaning parameters are undocumented in the schema. The description does not add any meaning to the parameters 'masterEditionId', 'page', or 'limit', failing to explain what they represent, their formats, or constraints. For a tool with 3 parameters and no schema documentation, this is inadequate compensation.

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 'NFT editions for a master edition', making the purpose specific and understandable. However, it does not differentiate from sibling tools like 'helius_get_asset' or 'helius_search_assets', which might also retrieve NFT-related data, so it lacks explicit sibling distinction.

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, such as other asset retrieval tools in the sibling list. It implies usage for fetching editions but offers no context on prerequisites, exclusions, or comparisons to similar tools, leaving the agent with minimal usage direction.

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