Skip to main content
Glama

List Hyperliquid perpetuals with funding and open interest

perps_markets
Read-only

Hyperliquid perpetual futures: mark and oracle price, hourly and annualised funding, open interest in coins and USD, 24 h volume and maximum leverage, sorted by volume. With coin, that market only. Public data, cached 30 seconds. Information only, not financial advice. Related tools on this server, for a different need: perps_account when you need a Hyperliquid account by address: account value, margin. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "perps_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoOptional symbol such as BTC or ETH
limitNo1 to 50 (default 10)

Output Schema

NameRequiredDescriptionDefault
sourceNo
marketsNo
checkedAtNo
disclaimerNo
marketCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes well beyond them: it discloses that the underlying data is public and cached 30 seconds (staleness the agent must account for), that the call costs $0.002 only on success with failures uncharged (retry-safety), and that output is informational, not advice. That is exactly the kind of operational context annotations cannot express.

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?

The payload (fields, sorting, filtering, caching, cost) is front-loaded before the routing and payment notes, with no filler sentences. It loses a point for running everything into one paragraph and spending several clauses enumerating payment networks, which is boilerplate relative to the tool's core purpose.

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 describe return values, and it still covers scope, filtering, staleness, cost, and sibling routing for a two-parameter read tool. Nothing an agent needs in order to call this correctly is missing.

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 baseline is 3, but "With coin, that market only" adds real meaning beyond the schema's 'Optional symbol such as BTC or ETH' by signalling that the response collapses to a single market instead of a list. The limit parameter's ordering and slicing behavior is left to the schema.

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 opening clause names the resource (Hyperliquid perpetual futures) and enumerates exactly what is returned: mark/oracle price, hourly and annualised funding, open interest in coins and USD, 24h volume, max leverage, sorted by volume. It also explicitly distinguishes itself from perps_account, so the agent can choose without opening either schema.

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?

"With coin, that market only" gives a clear conditional on how to narrow scope, and the sibling pointer states the case that should route to perps_account instead. It does not address the other crypto-related siblings (crypto_funding, markets), so exclusions are partial rather than exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources