Skip to main content
Glama

helius_get_asset

Retrieve detailed information about a specific digital asset on the Solana blockchain using its unique identifier.

Instructions

Get details of a digital asset by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The main handler function that executes the tool logic by calling the Helius SDK's getAsset method with the provided asset ID and formatting the response.
    export const getAssetHandler = async (input: { id: string }): Promise<ToolResultSchema> => {
      try {
        const asset = await (helius as any as Helius).rpc.getAsset(input.id);
        return createSuccessResponse(`Asset details: ${JSON.stringify(asset, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting asset: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Defines the tool's name, description, and input schema (requiring an 'id' string).
    name: 'helius_get_asset',
    description: 'Get details of a digital asset by its ID',
    inputSchema: {
      type: 'object',
      properties: {
        id: { type: 'string' }
      },
      required: ['id']
    }
  • src/tools.ts:572-572 (registration)
    Registers the handler function for the 'helius_get_asset' tool name in the handlers dictionary.
    "helius_get_asset": helius.getAssetHandler,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get details'), implying it's likely safe and non-destructive, but doesn't cover aspects like rate limits, authentication needs, error handling, or what 'details' include (e.g., metadata, ownership). This leaves significant gaps for an agent to understand how to use it effectively.

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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently conveys the basic action without unnecessary elaboration, making it easy to parse quickly.

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 complexity of a digital asset lookup tool with no annotations, 1 parameter at 0% coverage, and no output schema, the description is insufficient. It doesn't explain what 'details' are returned, potential errors, or usage constraints, leaving the agent with inadequate information to invoke the tool correctly in 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?

The input schema has 1 parameter with 0% description coverage, and the description doesn't add any semantic details about the 'id' parameter. It doesn't explain what format the ID should be (e.g., a string identifier, numeric, or specific encoding), where to find it, or any validation rules. This fails to compensate for the low schema coverage.

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 clearly states the action ('Get details') and resource ('digital asset by its ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'helius_get_asset_batch' or 'helius_get_assets_by_owner', which also retrieve asset information but with different parameters or scopes.

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. For example, it doesn't specify if this is for single assets versus batches (contrast with 'helius_get_asset_batch') or when ID-based lookup is preferred over owner-based queries. The description lacks any context or exclusions.

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