Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_get_assets_by_group

Retrieve Solana assets filtered by a group key and value, with pagination support for efficient data access.

Instructions

Get assets by group key and value

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": {
      "groupKey": "<groupKey>",
      "groupValue": "<groupValue>"
    },
    "name": "helius_get_assets_by_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupKeyYes
groupValueYes
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention any side effects, return type, pagination behavior, or rate limits. The tool appears to be a read operation, but this is not explicitly stated.

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, concise and efficient. It front-loads the core purpose. However, it is too brief to cover necessary details, leaving significant gaps.

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 4 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain how to use 'groupKey' and 'groupValue', what a group is, pagination behavior, or what the response contains. An agent would lack essential context to invoke the tool correctly.

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?

With 0% schema description coverage, the description must add meaning beyond parameter names. It only says 'by group key and value', providing no explanation of what 'groupKey' and 'groupValue' represent, acceptable formats, or the optional 'page' and 'limit' parameters. The names are self-explanatory but insufficient.

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 states the verb 'Get assets' and the resource 'by group key and value', clearly indicating the tool's purpose. However, it does not distinguish this from sibling tools like 'helius_get_assets_by_authority' or 'helius_search_assets', which also retrieve assets by different criteria.

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. It does not mention prerequisites, limitations, or scenarios where it is preferred over siblings like 'helius_get_assets_by_owner' or 'helius_search_assets'.

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