Skip to main content
Glama

Helius Asset

helius_asset
Read-onlyIdempotent

Details for a Solana asset/mint, full Digital Asset Standard (DAS) record for a single token or NFT by its mint address: metadata (name/symbol/interface), current ownership, royalty config, and supply. Example: helius_asset({ id: "F9Lw3ki3hJ7PF9HQXsBzoY8GyE6sPoEZZdXJBsTTD2rk", _apiKey: "your-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "F9Lw3ki3hJ7PF9HQXsBzoY8GyE6sPoEZZdXJBsTTD2rk",
      "_apiKey": "your-helius-api-key"
    },
    "name": "helius_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAsset ID, typically the mint address of the token/NFT (base58)
_apiKeyYesHelius API key (free 1M credits/mo at helius.dev)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Asset ID — typically the mint address of the token/NFT (base58)"New value: +"Asset ID, typically the mint address of the token/NFT (base58)"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description adds value by enumerating the returned record (metadata, ownership, royalty config, supply), but says nothing about credit cost, error/not-found behavior, or whether results are cached.

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 core purpose and returned fields are front-loaded in one dense sentence, followed by a usage example. The example largely duplicates the schema's built-in example, which is the only mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only single-record lookup with full annotation coverage and no output schema, listing the record's contents compensates well for the missing return schema. The only real gap is the absence of any statement about behavior when the mint is invalid or unknown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, including the base58 mint-address semantics for 'id' and the API-key note. The description restates the mint-address meaning and the inline example mirrors the schema's own example, adding little beyond the structured data.

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 names the resource precisely ('Solana asset/mint', 'full Digital Asset Standard (DAS) record') and narrows the scope to a single token or NFT looked up by mint address, which implicitly separates it from the owner-based sibling. It stops short of an explicit verb like 'retrieve' and never names an alternative, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through 'for a single token or NFT by its mint address' — an agent can infer this is the single-asset lookup versus a list-by-owner call. There is no explicit when-to-use/when-not statement, no mention of what to do if the asset does not exist, and no named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.