LiquidVision — Crypto Derivatives Data

get_hl_builder_markets

Read-onlyIdempotent

[measured] Perp markets deployed on Hyperliquid by third parties (HIP-3 builder dexs): equity indices, single stocks, commodities and pre-IPO names such as xyz:SP500 or xyz:GOLD. For each dex: its markets (coin named dex:COIN), open interest in USD (one side), 24h volume, mark price, hourly funding and its APR. These are NOT in get_open_interest or get_funding_rates, which cover Hyperliquid's own crypto listing. Live from Hyperliquid, cached 2 minutes. No arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hl_builder_markets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real value: the live data source (Hyperliquid), a 2-minute cache TTL, and units ('open interest in USD (one side)', hourly funding plus its APR). It stops short of describing ordering, per-dex field completeness, or failure behavior when a dex has no data.

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?

Front-loaded with scope, then return contents, then exclusions, then freshness, then 'No arguments.' Every sentence carries information; no filler or restatement of the tool name.

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?

For a no-arg read aggregator with no output schema, the description adequately covers what comes back (markets, OI, volume, mark, funding, APR) and how fresh it is. The only material omission is disambiguation from the near-identically named get_hip3_markets sibling, which is the main sourcing risk for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the baseline is 4, and the description closes the loop with 'No arguments.' That removes any doubt an agent might have about needing a dex filter.

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 names a specific verb and resource ('Perp markets deployed on Hyperliquid by third parties (HIP-3 builder dexs)') and enumerates the asset classes covered (equity indices, single stocks, commodities, pre-IPO). It even gives concrete identifier examples (xyz:SP500, xyz:GOLD) so an agent knows the coin naming format is dex:COIN.

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 explicitly carves out scope against siblings: 'These are NOT in get_open_interest or get_funding_rates, which cover Hyperliquid's own crypto listing' — a clear when-to-use signal. The gap is that the closest-sounding sibling, get_hip3_markets, is never mentioned, so an agent still has to guess between those two.

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

All LiquidVision — Crypto Derivatives Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?