Skip to main content
Glama

helius_get_assets_by_authority

Retrieve assets associated with a specific authority address on the Solana blockchain using Helius API data.

Instructions

Get assets by authority address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authorityYes
pageNo
limitNo

Implementation Reference

  • The main handler function that executes the tool logic by mapping input to Helius RPC call getAssetsByAuthority and returning the result.
    export const getAssetsByAuthorityHandler = async (input: GetAssetsByAuthorityInput): Promise<ToolResultSchema> => {
      try {
        // Fix the parameter name mismatch
        const params = {
          authorityAddress: input.authority, // Change authority to authorityAddress
          page: input.page || 1,
          limit: input.limit || 10
        };
        const assets = await (helius as any as Helius).rpc.getAssetsByAuthority(params);
        return createSuccessResponse(`Assets by authority: ${JSON.stringify(assets, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting assets by authority: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • JSON schema definition for the tool input validation.
    {
      name: 'helius_get_assets_by_authority',
      description: 'Get assets by authority address',
      inputSchema: {
        type: 'object',
        properties: {
          authority: { type: 'string' },
          page: { type: 'number' },
          limit: { type: 'number' }
        },
        required: ['authority']
      }
    },
  • src/tools.ts:579-579 (registration)
    Registration of the tool name to its handler function in the handlers dictionary.
    "helius_get_assets_by_authority": helius.getAssetsByAuthorityHandler,
  • TypeScript type definition for the handler input, matching the JSON schema.
    export type GetAssetsByAuthorityInput = {
      authority: string;
      page?: number;
      limit?: number;
    }
Behavior1/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 only states what the tool does ('Get assets'), with no information about whether this is a read-only operation, potential rate limits, authentication needs, pagination behavior (implied by 'page' and 'limit' parameters but not explained), or what happens on errors. This is inadequate for a tool with parameters and no annotation coverage.

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 zero wasted words. It's front-loaded with the core purpose, making it easy to scan, though this brevity comes at the cost of detail.

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 tool has 3 parameters with 0% schema coverage, no annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain parameter meanings, behavioral traits, or differentiation from similar tools, leaving significant gaps for the agent to operate effectively.

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?

Schema description coverage is 0%, meaning none of the 3 parameters ('authority', 'page', 'limit') are documented in the schema. The description only mentions 'authority address' without explaining what an authority is, its format, or how 'page' and 'limit' work for pagination. It fails to compensate for the complete lack of schema documentation.

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 authority address' clearly states the verb ('Get') and resource ('assets'), but it's vague about what 'assets' means in this context and doesn't differentiate from siblings like 'helius_get_assets_by_creator' or 'helius_get_assets_by_owner'. It provides basic purpose but lacks specificity about the type of assets or what 'authority' represents.

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_assets_by_creator' or 'helius_get_assets_by_owner'. The description doesn't mention prerequisites, exclusions, or contextual usage, leaving the agent to infer based on parameter names alone.

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