Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_get_assets_by_authority

Retrieve all digital assets (tokens, NFTs) associated with a specific Solana authority address, with pagination support for efficient data browsing.

Instructions

Get assets by authority address

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "authority": "<authority>"
    },
    "name": "helius_get_assets_by_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
authorityYes
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

The description lacks behavioral details beyond the basic operation. It does not mention pagination (page/limit parameters), whether results are ordered, response structure, or any side effects. With no annotations, the description carries full burden and fails to disclose these traits.

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 description is a single concise sentence with no extraneous content. However, it could benefit from minor expansion without harming conciseness (e.g., mentioning pagination). Overall, efficient and well-structured.

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?

For a paginated list endpoint with no output schema and minimal annotations, the description is insufficient. It does not explain return format, recommended usage patterns, or limitations. More context is needed to fully utilize the tool without external knowledge.

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?

Schema description coverage is 0%, and the description adds no explanation for any parameter. The 'authority' parameter is not defined; 'page' and 'limit' are self-explanatory but not elaborated. The description does not compensate for the missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action ('Get assets') and the resource ('by authority address'), distinguishing it from siblings like 'get_assets_by_owner' or 'get_assets_by_creator'. The verb+resource format is specific and unambiguous.

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 over alternatives. Siblings like 'get_assets_by_owner' and 'get_assets_by_creator' exist but the description gives no criteria for choosing this one.

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

Deploy Server

Other Tools