Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_get_nft_editions

Retrieve all editions belonging to a specific NFT master edition. Provide the master edition ID to get paginated results with page and limit parameters.

Instructions

Get NFT editions for a master edition

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": {
      "masterEditionId": "<masterEditionId>"
    },
    "name": "helius_get_nft_editions"
  }
}

Input Schema

NameRequiredDescriptionDefault
masterEditionIdYes
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior1/5

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

With no annotations, the description should reveal behavioral traits. It does not disclose pagination behavior, error conditions, or any side effects. The description is a bare statement of purpose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) and front-loaded, which is good for conciseness, but it lacks necessary detail. It is incomplete rather than concise.

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

Completeness1/5

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

Given the absence of annotations, output schema, and parameter descriptions, the description is severely incomplete. It fails to provide usage context, return value information, or any behavioral details needed for safe invocation.

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

Parameters1/5

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

The input schema has 0% description coverage and the description does not explain any parameters. The master edition ID is mentioned in the description context but not tied to the parameter. Page and limit are completely unexplained.

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 retrieves NFT editions for a master edition. It uses a specific verb and resource, and it distinguishes itself from sibling tools which are generally other query and action tools.

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_asset or helius_search_assets. There is no mention of prerequisites or typical scenarios.

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