Hyperliquid

Hyperliquid Mids

hyperliquid_mids

Read-onlyIdempotent

Live mid prices (midpoint of best bid/ask) for every asset Hyperliquid tracks — perps by symbol ("BTC", "ETH", ...) and spot pairs by numeric id ("@0", "@1", ...) — in one call, from Hyperliquid's public info API ({"type":"allMids"}). This is the cheapest way to get a current price: one request returns 1,000+ symbols. Pass coin to get just one symbol's mid price instead of the full map.

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": "ETH"
    },
    "name": "hyperliquid_mids"
  }
}

Input Schema

Name	Required	Description	Default
`coin`	No	Optional — return only this symbol's mid price, e.g. "BTC" or "ETH". Omit to get the full map.

Output Schema

Name	Required	Description	Default
`coin`	No
`as_of`	No
`found`	No
`source`	No
`mid_price`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations: it identifies the public info API call, explains that mids are midpoint of best bid/ask, and notes scale (1,000+ symbols). It does not discuss rate limits or error behavior, so it is strong but not exhaustive.

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 front-loaded with the core purpose and remains compact. Each sentence earns its place by adding scope, cost/scale context, or parameter behavior.

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?

With an output schema present, the description need not explain return values. It provides enough context about source API, scope, symbol formats, and full-vs-filtered behavior for an agent to invoke the tool correctly.

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?

Schema coverage is 100%, so the schema already documents the single optional `coin` parameter. The description still adds meaning by explaining full-map default behavior, single-symbol filtering, and the perp-vs-spot identifier formats ('BTC' vs '@0').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Live mid prices ... for every asset Hyperliquid tracks') and clarifies perp vs spot symbol formats. It does not explicitly name sibling tools such as hyperliquid_l2_book or hyperliquid_candles as alternatives, so sibling differentiation is implied rather than explicit.

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 gives clear usage context: use this as the cheapest way to get a current price, and pass `coin` to get one symbol instead of the full map. It does not explicitly state when not to use it or name alternative tools for order-book or historical data.

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.