Skip to main content
Glama
Sign In
Helius MCP

Helius MCP

Official
by helius-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ZK Compression

heliusCompression
Read-onlyIdempotent

Query Solana zk-compression state: compressed accounts, proofs, balances, token holders, and compression history. Use for compressed-account data, not standard DAS assets.

Instructions

Compressed account, proof, balance, and compression history queries. Use for zk-compression state, not standard DAS assets.

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": {
      "action": "<action>",
      "_feedback": "<_feedback>",
      "_feedbackTool": "<_feedbackTool>",
      "_model": "<_model>"
    },
    "name": "heliusCompression"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
hashNo
mintNo
limitNo
ownerNo
_modelYesLLM model identifier, for example claude-opus-4-6 or gpt-4o.
actionYes
cursorNo
detailNo
hashesNo
addressNo
delegateNo
_feedbackYesShort reason for this call or takeaway from the previous result, e.g. "initial balance check" or "balance looked healthy, checking history".
addressesNo
_feedbackToolYesCurrent public tool and action in "tool.action" form, e.g. "heliusWallet.getBalance".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / args / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "string"
+  }
+]
  2. First observedv2.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds almost no behavioral context beyond calling these queries: it does not mention indexing freshness, pagination, rate limits, auth requirements, or how action-specific behavior differs.

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

Conciseness5/5

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

Two short sentences, front-loaded with the resource scope and followed immediately by the routing exclusion. There is no redundant wording or filler.

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 tool with 23 actions, 15 parameters, low schema description coverage, and no output schema, the description is far too thin. It establishes the domain but leaves action selection, parameter requirements, and return behavior largely unexplained.

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 only 20%, so the description needs to compensate for undocumented parameters, but it does not explain action, hash, mint, owner, limit, cursor, detail, or the array parameters. It loosely groups query categories, yet gives no mapping from query type to required parameters or action selection.

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 names specific compressed-data resources (accounts, proofs, balances, compression history) and clarifies that this is for zk-compression state rather than standard DAS assets. That is enough to distinguish the domain from heliusAsset, though it does not identify a specific verb or enumerate the 23 action variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear when-to-use condition (zk-compression state) and an explicit exclusion (not standard DAS assets), which helps route away from asset-oriented siblings. It stops short of naming the alternative tool or explaining which action to choose for each query type.

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