Skip to main content
Glama

helius_search_assets

Search for Solana blockchain assets using filters such as owner address, creator, burnt status, frozen status, compressed, or supply mint. Retrieve paginated results.

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 actual handler function that executes the search_assets tool logic. Calls helius.rpc.searchAssets(input) and returns the results.
    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)}`);
      }
    }
  • Type definition for SearchAssetsInput, defining all supported search filter parameters.
    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:580-580 (registration)
    Registration of the 'helius_search_assets' tool mapping to helius.searchAssetsHandler in the tool registry.
    "helius_search_assets": helius.searchAssetsHandler,
  • Input schema definition for the 'helius_search_assets' tool, specifying all properties and validation constraints.
    {
      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'] }
        ]
      }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only says 'Search for assets'. It does not mention pagination (page, limit, cursor), read-only nature, or that at least one filter is required (anyOf). The minimal description lacks critical usage constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) but lacks structure and essential details. Conciseness does not compensate for under-specification; each word should earn its place, and here it fails to convey key information like required filters.

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 15 parameters, no annotations, and no output schema, the description is severely incomplete. An agent lacks the context to construct valid queries (e.g., anyOf constraint, pagination, filter combinations), making the tool nearly unusable.

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?

The input schema has 15 parameters with 0% description coverage, and the description adds no meaning beyond 'filters'. Without parameter descriptions, an agent cannot understand how to correctly use fields like grouping, supply, or compressed.

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 'Search for assets using various filters', which clearly indicates the tool's purpose as a general asset search. It distinguishes from sibling tools like get_asset (single) or get_assets_by_owner (specific filter), though it could be more specific about the asset type (e.g., Solana 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 is provided on when to use this tool versus the many sibling tools (e.g., get_assets_by_owner, get_assets_by_creator). The description lacks any context about the anyOf requirement or filtering strategies, making it hard for an agent to decide appropriateness.

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