Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_get_assets_by_creator

Retrieve all assets created by a given wallet address on Solana, with pagination support.

Instructions

Get assets created by a specific 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": {
      "creator": "<creator>"
    },
    "name": "helius_get_assets_by_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
creatorYes
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral transparency burden. It only states the basic function without disclosing pagination behavior (page/limit parameters), rate limits, or any potential side effects. The tool is essentially a query, but safety concerns are not addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (7 words), which is concise but at the cost of missing critical information. It is not well-structured beyond a single sentence.

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 lack of annotations, output schema, and the presence of many sibling tools (e.g., multiple get_assets_by_*), the description is incomplete. It does not cover return format, pagination, or distinctions from similar tools.

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%, and the description adds no meaning beyond the parameter names. For example, 'creator' is not explained (e.g., expected format like a base58 address), and 'page'/'limit' pagination semantics are absent.

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 'Get assets created by a specific address' uses a specific verb ('Get') and clearly identifies the resource and filter criterion. It differentiates well from siblings like 'helius_get_assets_by_owner' or 'helius_get_assets_by_authority'.

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 (e.g., 'helius_search_assets' for broader search or 'helius_get_assets_by_owner'). No when-not-to-use or prerequisites are mentioned.

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