Skip to main content
Glama

helius_get_rwa_asset

Retrieve detailed information about a specific real-world asset on the Solana blockchain by providing its unique identifier.

Instructions

Get details of a real-world asset by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • The getRwaAssetHandler function that executes the tool logic, calling Helius RPC to get RWA asset details by ID.
    export const getRwaAssetHandler = async (input: { id: string }): Promise<ToolResultSchema> => {
      try {
        const asset = await (helius as any as Helius).rpc.getRwaAsset({ id: input.id });
        return createSuccessResponse(`RWA Asset details: ${JSON.stringify(asset, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting RWA asset: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Input schema for the helius_get_rwa_asset tool defining the 'id' parameter.
    {
      name: 'helius_get_rwa_asset',
      description: 'Get details of a real-world asset by its ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string' }
        },
        required: ['id']
      }
    },
  • src/tools.ts:573-573 (registration)
    Maps the tool name 'helius_get_rwa_asset' to its handler in the handlers dictionary.
    "helius_get_rwa_asset": helius.getRwaAssetHandler,
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'gets details' but doesn't disclose behavioral traits such as read-only vs. mutative nature, authentication requirements, rate limits, error handling, or expected output format. This leaves significant gaps for an agent to understand how the tool behaves in practice.

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 no wasted words. It's front-loaded with the core action and resource, 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 asset retrieval in a blockchain context, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavior, parameter usage, output expectations, and differentiation from siblings, making it inadequate for reliable tool invocation.

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. It mentions 'by its ID' which adds some meaning to the 'id' parameter, but doesn't specify the format (e.g., string type, expected length, examples), constraints, or how it relates to real-world assets. This is insufficient given 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 verb ('Get details') and resource ('real-world asset by its ID'), making the purpose understandable. It distinguishes from generic 'helius_get_asset' by specifying 'real-world asset', but doesn't explicitly differentiate from other asset-related siblings like 'helius_get_assets_by_owner' or 'helius_search_assets' in terms of scope or use case.

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. With many sibling tools for asset retrieval (e.g., 'helius_get_asset', 'helius_get_assets_by_owner', 'helius_search_assets'), the description lacks context on prerequisites, typical scenarios, or comparisons to help the agent choose appropriately.

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