Skip to main content
Glama

Helius Parsed Transactions

helius_parsed_transactions
Read-onlyIdempotent

Parsed transaction history for a Solana address, human-readable, enriched tx feed (swaps, NFT sales, transfers) with a plain-English description, type, source protocol, fee, and timestamp for each transaction. Deeper than a raw signature list. Example: helius_parsed_transactions({ address: "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY", limit: 20, _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": {
      "limit": 20,
      "_apiKey": "your-helius-api-key",
      "address": "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY"
    },
    "name": "helius_parsed_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax transactions to return (default 20, max 50)
_apiKeyYesHelius API key (free 1M credits/mo at helius.dev)
addressYesSolana wallet or program address (base58), e.g. "86xCnPeV69n6t3DnyGvkKobf9FdN2H9oiVDdaMpo2MMY"

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 declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by describing the shape of each returned record, but it omits ordering (newest-first?), behavior past the 50-item cap, and credit consumption that the schema only hints at.

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 capability and the field list are front-loaded in the first sentence, with a concrete example following. The example slightly duplicates the schema's examples array but is short and does not bury the core claim.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by enumerating the per-transaction fields. For a single-address read tool this is nearly complete; ordering and behavior beyond the limit ceiling are the remaining gaps.

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 the schema already documents address, limit (default 20, max 50) and _apiKey. The description's inline example merely restates those values without adding format or edge-case detail, so the baseline 3 applies.

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 opens with a specific verb+resource ('Parsed transaction history for a Solana address') and enumerates the enriched fields returned (type, source protocol, fee, timestamp, plain-English description). It implicitly differentiates itself from a raw signature feed, though it never names a sibling tool such as helius_asset or helius_assets_by_owner, so an agent must infer the boundary.

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?

The phrase 'Deeper than a raw signature list' gives implied guidance about when this is preferable, but there is no explicit when-to-use/when-not-to-use statement, no prerequisites, and no named alternative for the case where the agent only needs signatures or asset metadata.

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.