Skip to main content
Glama

helius_get_assets_by_group

Retrieve digital assets from the Solana blockchain by specifying a group category and value, enabling targeted queries for tokens and NFTs based on shared attributes.

Instructions

Get assets by group key and value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupKeyYes
groupValueYes
pageNo
limitNo

Implementation Reference

  • The handler function that executes the tool logic: validates input, calls Helius RPC getAssetsByGroup, and returns formatted success or error response.
    export const getAssetsByGroupHandler = async (input: { groupKey: string, groupValue: string, page?: number, limit?: number }): Promise<ToolResultSchema> => {
      try {
        // Fix the parameter type mismatch
        const params = {
          groupKey: input.groupKey,
          groupValue: input.groupValue,
          page: input.page || 1, // Default to page 1 if not provided
          limit: input.limit || 10 // Default to 10 if not provided
        };
        const assets = await (helius as any as Helius).rpc.getAssetsByGroup(params);
        return createSuccessResponse(`Assets by group: ${JSON.stringify(assets, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting assets by group: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The tool schema defining name, description, and input validation schema.
    {
      name: 'helius_get_assets_by_group',
      description: 'Get assets by group key and value',
      inputSchema: {
        type: 'object',
        properties: {
          groupKey: { type: 'string' },
          groupValue: { type: 'string' },
          page: { type: 'number' },
          limit: { type: 'number' }
        },
        required: ['groupKey', 'groupValue']
      }
    },
  • src/tools.ts:576-576 (registration)
    Registration of the tool name to its handler function in the central handlers dictionary.
    "helius_get_assets_by_group": helius.getAssetsByGroupHandler,
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get assets' which implies a read operation, but doesn't disclose behavioral traits such as pagination handling (implied by 'page' and 'limit' parameters), rate limits, authentication needs, or what format/assets are returned. The description adds minimal value beyond the tool name.

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 with no wasted words. It's appropriately sized and front-loaded, directly stating the tool's core function without unnecessary elaboration.

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 4 parameters with 0% schema coverage, no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain the context of 'group' filtering, parameter usage, or return values, making it inadequate for an agent to use this tool effectively 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%, so the description must compensate. It mentions 'group key and value', which maps to the required parameters 'groupKey' and 'groupValue', but doesn't explain what these represent (e.g., types of groups, examples) or the optional 'page' and 'limit' parameters. This leaves significant gaps in parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get assets by group key and value' clearly states the verb ('Get') and resource ('assets'), but it's vague about what 'group' means in this context. It distinguishes from some siblings like 'helius_get_assets_by_owner' by specifying 'by group', but doesn't clarify what constitutes a group versus other filtering methods (e.g., owner, creator, authority).

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. With siblings like 'helius_get_assets_by_owner', 'helius_get_assets_by_creator', and 'helius_search_assets', the description lacks any indication of when 'group' filtering is appropriate or what distinguishes it from other asset retrieval methods.

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