Skip to main content
Glama

Helius Assets By Owner

helius_assets_by_owner
Read-onlyIdempotent

Tokens & NFTs owned by a Solana wallet, lists every digital asset (fungible tokens, regular + compressed NFTs) held by an address via the Digital Asset Standard (DAS), with name, symbol, balance, and interface type. Example: helius_assets_by_owner({ address: "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY", _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": {
      "_apiKey": "your-helius-api-key",
      "address": "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY"
    },
    "name": "helius_assets_by_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesHelius API key (free 1M credits/mo at helius.dev)
addressYesSolana wallet address (base58) whose assets to list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already carry the safety profile (readOnlyHint, idempotentHint, non-destructive, open-world), so the description's remaining job is operational detail. It adds that DAS is the backing standard and enumerates returned fields, which is useful, but says nothing about result limits/pagination or behavior for a wallet with thousands of assets — a meaningful gap for a list endpoint.

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?

A single front-loaded sentence followed by a short example, with no filler. The example is largely redundant with the schema's own 'examples' block, costing a little space without adding new information.

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 low-complexity, two-parameter read tool with full schema coverage and rich annotations, the description covers purpose and return-field shape well. The missing piece is pagination/limit behavior, which matters for an unbounded wallet-holdings query.

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 (address, _apiKey) are already documented with base58 format and API-key sourcing. The description adds nothing beyond the schema; the inline example merely restates the same two fields already present in the schema's examples array.

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?

States a specific verb and resource — lists every digital asset (fungible tokens, regular and compressed NFTs) held by a Solana address via DAS — and names the returned fields. Scope is clear enough to distinguish it from a single-asset lookup, though no sibling is named explicitly.

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: call it when you need a wallet's full holdings rather than one asset. There is no explicit when-to-use vs. the sibling helius_asset, and no guidance on when the result set would be truncated or how to page through a large wallet.

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.