Skip to main content
Glama
subsquid-labs

SQD

Official
by subsquid-labs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Chart Hyperliquid prices

portal_hyperliquid_get_ohlc
Read-only

Generate chart-ready Hyperliquid OHLC candles with volume and VWAP from trade fills. Use fixed buckets or auto intervals for any asset to get chart data quickly.

Instructions

Build chart-ready Hyperliquid trade OHLC candles with fixed buckets and auto intervals.

COMMON USER ASKS:

  • BTC candles

WHEN TO USE:

  • You want candles for one coin on Hyperliquid.

  • You need chart-ready OHLC, volume, and VWAP data from fills.

DON'T USE:

  • You want scalar time-series buckets or raw fills.

EXAMPLES:

  • BTC candles: {"network":"hyperliquid-fills","coin":"BTC","duration":"6h","interval":"auto"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoAsset symbol to build candles for (for example: "BTC", "ETH", "SOL"). Optional when continuing with cursor.
userNoOptional trader wallet address (0x-prefixed, lowercase)
cursorNoContinuation cursor from a previous candle page
networkNoNetwork name (default: 'hyperliquid-fills')hyperliquid-fills
durationNoHow much recent trading history to cover. Accepts compact durations like "1h" or natural phrases like "past 30 minutes".1h
intervalNoCandle interval. Use auto for chart-friendly defaults: 1h→5m, 6h→15m, 12h→30m, 24h→1h.auto

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_uiNoOptional chart, table, and follow-up presentation metadata.
_llmNoHints that help an AI client locate the primary evidence.
_metaNoNetwork, block range, timing, and row-count metadata.
errorNoStructured failure details when the tool cannot complete the request.
itemsNoPrimary result rows when the tool returns a list.
valueNoPrimary result when the tool returns a scalar value.
answerNoConcise answer grounded in the returned blockchain data.
_noticeNoImportant limitation or truncation notice.
displayNoPlain-language labels for presenting the result.
_noticesNoImportant limitations or truncation notices.
_summaryNoHuman-readable summary of the result.
_coverageNoCompleteness of the requested window and result set.
_evidenceNoReplayable arguments, exact-data digest, row count, and completeness receipt.
_orderingNoOrdering guarantees for the returned data.
_executionNoBounded execution and scan details.
_freshnessNoFreshness and finality information for the returned data.
next_stepsNoSafe follow-up actions and continuation guidance.
_paginationNoPagination state and an optional continuation cursor.
investigationNoEvidence paths, useful pivots, and result limitations.
pipes_handoffNoOptional SQD Pipes guidance for custom data needs.
_tool_contractNoTool identity, intent, and supported blockchain families.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.8.3
    • addedOutput schema / properties / _evidence
      Added value: +{
+  "additionalProperties": {},
+  "description": "Replayable arguments, exact-data digest, row count, and completeness receipt.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changedv0.8.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_coverage": {
+      "description": "Completeness of the requested window and result set."
+    },
+    "_execution": {
+      "additionalProperties": {},
+      "description": "Bounded execution and scan details.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_freshness": {
+      "description": "Freshness and finality information for the returned data."
+    },
+    "_llm": {
+      "description": "Hints that help an AI client locate the primary evidence."
+    },
+    "_meta": {
+      "additionalProperties": {},
+      "description": "Network, block range, timing, and row-count metadata.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_notice": {
+      "description": "Important limitation or truncation notice.",
+      "type": "string"
+    },
+    "_notices": {
+      "description": "Important limitations or truncation notices.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "_ordering": {
+      "description": "Ordering guarantees for the returned data."
+    },
+    "_pagination": {
+      "additionalProperties": {},
+      "description": "Pagination state and an optional continuation cursor.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_summary": {
+      "description": "Human-readable summary of the result.",
+      "type": "string"
+    },
+    "_tool_contract": {
+      "additionalProperties": {},
+      "description": "Tool identity, intent, and supported blockchain families.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "_ui": {
+      "description": "Optional chart, table, and follow-up presentation metadata."
+    },
+    "answer": {
+      "description": "Concise answer grounded in the returned blockchain data.",
+      "type": "string"
+    },
+    "display": {
+      "additionalProperties": {},
+      "description": "Plain-language labels for presenting the result.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": {},
+      "description": "Structured failure details when the tool cannot complete the request.",
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "origin": {
+          "type": "string"
+        },
+        "retry_after_ms": {
+          "type": "number"
+        },
+        "retryable": {
+          "type": "boolean"
+        },
+        "suggestions": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "summary": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "origin",
+        "summary",
+        "retryable",
+        "suggestions"
+      ],
+      "type": "object"
+    },
+    "investigation": {
+      "additionalProperties": {},
+      "description": "Evidence paths, useful pivots, and result limitations.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "items": {
+      "description": "Primary result rows when the tool returns a list.",
+      "items": {},
+      "type": "array"
+    },
+    "next_steps": {
+      "additionalProperties": {},
+      "description": "Safe follow-up actions and continuation guidance.",
+      "properties": {
+        "actions": {
+          "items": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "continuation": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        },
+        "custom_data": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "actions"
+      ],
+      "type": "object"
+    },
+    "pipes_handoff": {
+      "description": "Optional SQD Pipes guidance for custom data needs."
+    },
+    "value": {
+      "description": "Primary result when the tool returns a scalar value."
+    }
+  },
+  "type": "object"
+}
  3. First observedv0.7.9

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide safety context (readOnlyHint=true, destructiveHint=false), so the description only needs to add behavioral value. It does so by explaining that candles are derived from fills, are chart-ready, use fixed buckets and auto intervals, and include volume and VWAP. Minor details like pagination and the optional user scope are left to the schema, which is acceptable given the annotation coverage.

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?

The description is well-structured with clearly labeled sections: common asks, when to use, when not to use, and an example. It is front-loaded with the core purpose and every section earns its place without unnecessary fluff.

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

Completeness5/5

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

For a read-only OHLC tool with full schema coverage, an output schema, and explicit usage guidance, the description is complete. It includes an example payload, clear exclusions, and the source of the data, so an agent has enough context to select and invoke the tool correctly.

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 all six parameters. The description adds conceptual context (chart-ready, fixed buckets, auto intervals) and a concrete example, but it does not add parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource: "Build chart-ready Hyperliquid trade OHLC candles with fixed buckets and auto intervals." It clearly states the output type, source data, and scoping, and the DON'T USE section distinguishes it from scalar time-series and raw fills, so an agent can separate it from siblings like portal_get_time_series and portal_hyperliquid_query_fills.

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?

Explicit WHEN TO USE and DON'T USE sections give clear selection criteria: use for per-coin Hyperliquid candles with chart-ready OHLC/volume/VWAP, avoid for raw fills or scalar buckets. However, it does not name the specific alternative tools to use in those excluded cases, so it falls just short of the highest bar.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/subsquid-labs/portal-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server