Skip to main content
Glama

helius_get_assets_by_owner

Retrieve assets owned by a specific wallet address on Solana. Supports pagination to navigate large collections.

Instructions

Get assets owned by a specific address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
pageNo
limitNo

Implementation Reference

  • The handler function that executes the 'helius_get_assets_by_owner' tool logic. It validates the owner address via schema, maps 'owner' to 'ownerAddress' parameter, calls the Helius SDK's getAssetsByOwner RPC method, and returns the result.
    export const getAssetsByOwnerHandler = async (input: { owner: string, page?: number, limit?: number }): Promise<ToolResultSchema> => {
      try {
        // Fix the parameter name mismatch
        const params = {
          ownerAddress: input.owner, // Change owner to ownerAddress
          page: input.page || 1,
          limit: input.limit || 10
        };
        const assets = await (helius as any as Helius).rpc.getAssetsByOwner(params);
        return createSuccessResponse(`Assets by owner: ${JSON.stringify(assets, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting assets by owner: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The tool definition and input schema for 'helius_get_assets_by_owner', specifying 'owner' (required), 'page', and 'limit' as input properties.
    {
      name: 'helius_get_assets_by_owner',
      description: 'Get assets owned by a specific address',
      inputSchema: {
        type: 'object',
        properties: {
          owner: { type: 'string' },
          page: { type: 'number' },
          limit: { type: 'number' }
        },
        required: ['owner']
      }
    },
  • src/tools.ts:577-577 (registration)
    The registration of 'helius_get_assets_by_owner' mapping the tool name to its handler function 'helius.getAssetsByOwnerHandler' in the handlers dictionary.
    "helius_get_assets_by_owner": helius.getAssetsByOwnerHandler,
Behavior2/5

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

With no annotations, the description carries full burden. It doesn't disclose behavioral traits such as pagination (despite page/limit parameters), rate limits, or response format (e.g., whether it returns metadata, images). The simple 'get' statement is insufficient for a realistic tool.

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 concise sentence with no wasted words. It earns its place by being brief, though at the cost of 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 3 parameters, no output schema, and many sibling tools, the description is incomplete. It doesn't explain pagination, asset types, or contrast with alternatives. The agent lacks critical information for correct usage.

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 has 0% description coverage. The description adds no meaning to parameters; it doesn't explain what 'owner' format is acceptable (address), or how 'page' and 'limit' control pagination. The agent must infer from names alone.

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 'Get assets owned by a specific address' clearly states the action (get) and the resource (assets by owner). It distinguishes from siblings like 'helius_get_asset' (single asset) or 'helius_get_assets_by_authority' (different filter), though it doesn't specify types of assets.

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 on when to use this tool versus alternatives like 'helius_get_assets_by_creator' or 'helius_search_assets'. The description provides no context for selection, leaving the agent without decision support.

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