Hyperliquid

Hyperliquid Asset Context

hyperliquid_asset_context

Read-onlyIdempotent

Live perp market context for one contract — current funding rate, open interest, mark price, oracle price, mid price, 24h premium, and 24h notional + base volume — from Hyperliquid's public info API ({"type":"metaAndAssetCtxs"}, matched to the requested coin by universe index). This is the single call that answers "what is BTC perp funding right now" or "what is Hyperliquid's open interest in ETH" — the live numbers next to kalshi_* and polymarket_* for anyone pricing crypto-adjacent prediction markets. For a HISTORY of funding rates rather than the current one, use hyperliquid_funding_history.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description	Default
`coin`	Yes	Perp symbol, e.g. "BTC", "ETH", "SOL". See hyperliquid_perp_meta for the full list.

Output Schema

Name	Required	Description	Default
`coin`	No
`as_of`	No
`found`	No
`source`	No
`premium`	No
`mid_price`	No
`mark_price`	No
`funding_rate`	No
`max_leverage`	No
`oracle_price`	No
`open_interest`	No
`prev_day_price`	No
`day_base_volume`	No
`funding_rate_note`	No
`open_interest_unit`	No
`day_notional_volume_usd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 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/destructive=false, so the safety profile is covered. The description adds real value beyond that: it names the upstream call ({"type":"metaAndAssetCtxs"}) and discloses the matching mechanism (universe index), which tells the agent how the coin resolves. It says nothing about freshness, caching or error behavior for an unknown symbol.

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

Conciseness4/5

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

Front-loaded with the resource and field list, then usage framing, then the exclusion. The one weaker sentence is the kalshi_*/polymarket_* positioning aside, which is more pitch than instruction, but it does convey cross-tool context.

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?

An output schema exists, so return shape needn't be described; the description still enumerates the returned fields. With one required param, full schema coverage, annotations and an explicit sibling exclusion, an agent has everything needed to select and call this 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% and the single `coin` parameter is already documented with examples and a pointer to hyperliquid_perp_meta. The description only restates that the coin is matched by universe index, adding no new parameter-level detail. Baseline 3 applies.

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?

States a specific verb+resource (live perp market context for one contract) and enumerates exactly which fields come back: funding rate, open interest, mark/oracle/mid price, 24h premium and volume. It also distinguishes itself from hyperliquid_funding_history in the same breath.

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?

Explicitly names the questions this answers ("what is BTC perp funding right now") and gives an exclusion plus a named alternative ("For a HISTORY of funding rates rather than the current one, use hyperliquid_funding_history"). Little is left to inference.

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

All Hyperliquid 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.