SQD

by io.github.subsquid-labs

Inspect Hyperliquid command records

portal_debug_hyperliquid_query_replica_commands

Read-only

ADVANCED: Query Hyperliquid replica-command actions such as orders, cancels, and leverage updates.

COMMON USER ASKS:

Recent order action

WHEN TO USE:

You are debugging Hyperliquid replica-command records.
You need raw order-action events instead of fills or analytics.

DON'T USE:

You only need public trading activity; fills and analytics are usually the better fit.

EXAMPLES:

Recent order action: {"network":"hyperliquid-replica-cmds","timeframe":"5m","limit":1}

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user`	No	User wallet addresses (0x-prefixed, lowercase)
`limit`	No	Max actions to return (1). Replica command payloads can contain large batches, so this exact one-record cursor page is the verified safe response budget.
`cursor`	No	Continuation cursor from a previous response
`status`	No	Filter by action status
`network`	No	Network name (default: 'hyperliquid-replica-cmds'). Optional when continuing with cursor.	hyperliquid-replica-cmds
`to_block`	No	Ending block number
`timeframe`	No	Time range (e.g., '1h', '24h'). Alternative to from_block/to_block.
`from_block`	No	Starting block number (use this OR timeframe)
`action_type`	No	Action types to filter
`to_timestamp`	No	Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
`vault_address`	No	Vault addresses (0x-prefixed, lowercase)
`finalized_only`	No	Only query finalized blocks
`from_timestamp`	No	Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".

Output Schema

TableJSON Schema

Name	Required	Description
`_ui`	No	Optional chart, table, and follow-up presentation metadata.
`_app`	No	SQD Explorer identity and honest host-render state.
`_llm`	No	Hints that help an AI client locate the primary evidence.
`_meta`	No	Network, block range, timing, and row-count metadata.
`error`	No	Structured failure details when the tool cannot complete the request.
`items`	No	Primary result rows when the tool returns a list.
`value`	No	Primary result when the tool returns a scalar value.
`answer`	No	Concise answer grounded in the returned blockchain data.
`_notice`	No	Important limitation or truncation notice.
`_server`	No	Observable SQD server identity and exact release version.
`display`	No	Plain-language labels for presenting the result.
`_notices`	No	Important limitations or truncation notices.
`_summary`	No	Human-readable summary of the result.
`_coverage`	No	Completeness of the requested window and result set.
`_evidence`	No	Replayable arguments, exact-data digest, row count, and completeness receipt.
`_ordering`	No	Ordering guarantees for the returned data.
`_execution`	No	Bounded execution and scan details.
`_freshness`	No	Freshness and finality information for the returned data.
`next_steps`	No	Safe follow-up actions and continuation guidance.
`_pagination`	No	Pagination state and an optional continuation cursor.
`investigation`	No	Evidence paths, useful pivots, and result limitations.
`pipes_handoff`	No	Optional SQD Pipes guidance for custom data needs.
`_tool_contract`	No	Tool identity, intent, and supported blockchain families.

Schema Changelog

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

Changed2 schema fields changedSep 1, 2026

changedOutput schema / properties / _app / description

Previous value: -"SQD Blockchain Activity Explorer identity and honest host-render state."New value: +"SQD Explorer identity and honest host-render state."

addedOutput schema / properties / _server

Added value: +{
+  "additionalProperties": false,
+  "description": "Observable SQD server identity and exact release version.",
+  "properties": {
+    "name": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version"
+  ],
+  "type": "object"
+}

Changed6 schema fields changedAug 31, 2026

changedInput schema / properties / limit / default
```
Previous value: -50New value: +1
```

changedInput schema / properties / limit / description

Previous value: -"Max actions to return"New value: +"Max actions to return (1). Replica command payloads can contain large batches, so this exact one-record cursor page is the verified safe response budget."

addedInput schema / properties / limit / maximum
```
Added value: +1
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedOutput schema / properties / _app

Added value: +{
+  "additionalProperties": {},
+  "description": "SQD Blockchain Activity Explorer identity and honest host-render state.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 30, 2026

addedOutput schema / properties / _evidence

Added value: +{
+  "additionalProperties": {},
+  "description": "Replayable arguments, exact-data digest, row count, and completeness receipt.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed1 schema field changedAug 28, 2026

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"
+}

Changed6 schema fields changedAug 27, 2026

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
```

addedInput schema / properties / from_timestamp / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / from_timestamp / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

addedInput schema / properties / to_timestamp / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / to_timestamp / type
```
Removed value: -[
-  "number",
-  "string"
-]
```

First observedJun 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by emphasizing these are raw replica-command actions rather than derived fills/analytics, plus an ADVANCED warning and a concrete example invocation.

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-organized with clear headings, front-loads the core query purpose, provides a concrete example, and has no filler. Every section earns its place, and the example is directly actionable.

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?

Given the 13-parameter schema with full parameter descriptions, a rich output schema, and annotations covering read-only safety, the description provides sufficient orientation. It adds selection guidance, exclusions, and an example, so nothing critical is missing for an agent to invoke this 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?

Input schema coverage is 100%, with every parameter individually described. The description adds a useful example JSON and mentions action types like orders, cancels, and leverage updates, but it does not substantially enrich parameter semantics beyond what the schema already provides.

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?

Description states a specific verb and resource: 'Query Hyperliquid replica-command actions such as orders, cancels, and leverage updates.' It also differentiates from sibling tools by noting this is for raw order-action events rather than fills or analytics, making it easy to distinguish.

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

Usage Guidelines5/5

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

WHEN TO USE and DON'T USE sections explicitly state the usage context: debugging Hyperliquid replica-command records and needing raw order-action events. It also names excluded cases ('fills and analytics are usually the better fit'), giving clear alternative routing.

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

All SQD tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Each VM has a parallel analytics/query family, but the network and object names keep most tools clearly separated. A few near-overlaps exist (evm_query_logs vs evm_query_token_transfers; get_head vs get_network_info; get_recent_activity vs raw query tools), though the usage notes provide good disambiguation.

Naming Consistency5/5

All tools follow the same snake_case portal_<vm>_<verb>_<object> pattern, with get used for summaries, query for raw records, and a consistent debug prefix for advanced/internal tools. The naming is highly predictable.

Tool Count2/5

At 28 tools the set is above the 25+ threshold and feels heavy even though the multi-chain scope explains much of the mass. The five network analytics and multiple raw query tools could be consolidated, but the count is not extreme.

Completeness4/5

The surface covers analytics, raw transactions/logs/calls/events/fills, time series, wallet summaries, entity resolution, and network freshness information across several ecosystems. Obvious gaps are minor: no convenient transaction-by-hash or block-by-number lookup outside the debug tools, and wallet summary coverage is not uniformly demonstrated for every VM.

Inspect Hyperliquid command records

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources