Skip to main content
Glama
Sign In
MCP Helius

MCP Helius

by dcSpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

helius_get_signatures_for_asset

Retrieve all transaction signatures for a specific digital asset on Solana to track its history and interactions.

Instructions

Get signatures associated with an asset

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": {
      "id": "<id>"
    },
    "name": "helius_get_signatures_for_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as pagination, rate limits, or the nature of the returned signatures. The tool's behavior is opaque.

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 a single sentence, making it concise, but it sacrifices informative structure. It is not verbose, but could be more structured with additional details.

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

Completeness1/5

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

Given the complexity of three parameters, no output schema, and many sibling tools, the description is severely incomplete. It lacks information on pagination, return format, and differentiation from similar tools.

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 does not explain any of the three parameters (id, page, limit). The purpose of each parameter is entirely unclear from the description.

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 it retrieves signatures for an asset, which is a specific verb+resource. However, given the sibling tool 'helius_get_signatures_for_address', the description could explicitly distinguish between asset and address contexts.

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 on when to use this tool over alternatives like 'helius_get_signatures_for_address'. No context on prerequisites or typical use cases.

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