Skip to main content
Glama

portal_debug_hyperliquid_query_replica_commands

Debug Hyperliquid replica commands by querying raw order, cancel, and leverage update actions.

Instructions

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

COMMON USER ASKS:

  • Recent order actions

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 actions: {"network":"hyperliquid-replica-cmds","timeframe":"1h","limit":20}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoUser wallet addresses (0x-prefixed, lowercase)
limitNoMax actions to return
cursorNoContinuation cursor from a previous response
statusNoFilter by action status
networkNoNetwork name (default: 'hyperliquid-replica-cmds'). Optional when continuing with cursor.hyperliquid-replica-cmds
to_blockNoEnding block number
timeframeNoTime range (e.g., '1h', '24h'). Alternative to from_block/to_block.
from_blockNoStarting block number (use this OR timeframe)
action_typeNoAction types to filter
to_timestampNoEnding timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now".
vault_addressNoVault addresses (0x-prefixed, lowercase)
finalized_onlyNoOnly query finalized blocks
from_timestampNoStarting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago".
Behavior3/5

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

No annotations provided, so description carries burden. It implies read-only via 'Query', but does not explicitly state safety, rate limits, or other behavioral traits. Minimal extra disclosure beyond the operation type.

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?

Well-structured with sections (common asks, when/don't use, example). Every sentence adds value, front-loaded with purpose. No wasted words.

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?

Given 13 parameters and no output schema, description effectively covers scope, usage, and provides an example. Could mention output format, but overall complete enough for a query tool with good schema documentation.

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 baseline is 3. Description adds only an example usage, not additional meaning beyond what schema provides. Example is helpful but not extensive.

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 clearly states the tool queries Hyperliquid replica-command actions (orders, cancels, leverage updates) and contrasts with fills/analytics, distinguishing it from sibling tools like 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 Guidelines5/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 provide clear context: use for debugging replica-command records, avoid for public trading activity (fills/analytics better suited).

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