Skip to main content
Glama

helius_search_assets

Search for Solana blockchain assets using filters like owner address, creator, or metadata to find specific tokens and NFTs.

Instructions

Search for assets using various filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNo
cursorNo
beforeNo
afterNo
creatorAddressNo
ownerAddressNo
jsonUriNo
groupingNo
burntNo
frozenNo
supplyMintNo
supplyNo
delegateNo
compressedNo

Implementation Reference

  • The handler function that executes the tool logic by calling the Helius SDK's rpc.searchAssets method with the input parameters.
    export const searchAssetsHandler = async (input: SearchAssetsInput): Promise<ToolResultSchema> => {
      try {
        const assets = await (helius as any as Helius).rpc.searchAssets(input);
        if (!assets || assets.items.length === 0) {
          return createErrorResponse(`No assets found for search: ${JSON.stringify(input, null, 2)}`);
        }
        return createSuccessResponse(`Search results: ${JSON.stringify(assets, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error searching assets: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The input schema definition for the helius_search_assets tool, defining all possible search filters and validation rules.
    {
      name: 'helius_search_assets',
      description: 'Search for assets using various filters',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number' },
          limit: { type: 'number' },
          cursor: { type: 'string' },
          before: { type: 'string' },
          after: { type: 'string' },
          creatorAddress: { type: 'string' },
          ownerAddress: { type: 'string' },
          jsonUri: { type: 'string' },
          grouping: { 
            type: 'array',
            items: { type: 'string' }
          },
          burnt: { type: 'boolean' },
          frozen: { type: 'boolean' },
          supplyMint: { type: 'string' },
          supply: { type: 'number' },
          delegate: { type: 'string' },
          compressed: { type: 'boolean' }
        },
        // At least one filter parameter should be provided
        anyOf: [
          { required: ['ownerAddress'] },
          { required: ['creatorAddress'] },
          { required: ['jsonUri'] },
          { required: ['supplyMint'] },
          { required: ['delegate'] },
          { required: ['burnt'] },
          { required: ['frozen'] },
          { required: ['compressed'] }
        ]
      }
    },
  • src/tools.ts:580-580 (registration)
    Registration of the tool name mapping to its handler function in the handlers dictionary.
    "helius_search_assets": helius.searchAssetsHandler,
  • TypeScript type definition for the SearchAssetsInput used in the handler.
    export type SearchAssetsInput = {
      page?: number;
      limit?: number;
      cursor?: string;
      before?: string;
      after?: string;
      creatorAddress?: string;
      ownerAddress?: string;
      jsonUri?: string;
      grouping?: string[];
      burnt?: boolean;
      frozen?: boolean;
      supplyMint?: string;
      supply?: number;
      delegate?: string;
      compressed?: boolean;
    }
  • src/tools.ts:1-1 (registration)
    Import of the helius module containing the searchAssetsHandler.
    import * as helius from './handlers/helius.js';
Behavior2/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 mentions 'search' and 'filters', but doesn't describe key behaviors like pagination handling (implied by 'page', 'limit', 'cursor' parameters), rate limits, authentication needs, or what 'assets' encompasses. For a tool with 15 parameters and no annotation coverage, this is a significant gap in transparency.

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, efficient sentence with no wasted words. It's appropriately sized for a basic overview, though it could be more front-loaded with critical details given the tool's complexity. The brevity is a strength, but it borders on under-specification.

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 high complexity (15 parameters, no output schema, 0% schema coverage, no annotations), the description is incomplete. It doesn't explain the tool's scope, return format, error conditions, or how it differs from sibling asset retrieval tools. For a search tool with rich filtering options, more context is needed to guide effective use.

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 by explaining parameters. It only vaguely mentions 'various filters', without detailing what filters are available (e.g., ownerAddress, burnt status) or their semantics. With 15 parameters, this leaves most input meaning undocumented, failing to add value beyond the bare schema.

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 'Search for assets using various filters' states a clear verb ('search') and resource ('assets'), but it's vague about what 'assets' means in this context (e.g., NFTs, tokens, or general blockchain assets). It doesn't differentiate from sibling tools like 'helius_get_assets_by_owner' or 'helius_get_asset', which also retrieve asset information, leaving ambiguity about when to use this versus those alternatives.

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. With many sibling tools like 'helius_get_assets_by_owner' and 'helius_get_asset', there's no indication of when this search tool is preferred (e.g., for complex filtering across multiple criteria). It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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