Skip to main content
Glama
samklein952-hub

Hyperliquid MCP Server

list_markets

Retrieve all perpetual futures markets available for trading on the Hyperliquid exchange to view current trading options.

Instructions

List all available perpetual futures markets on Hyperliquid

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The list_markets handler function that fetches all available perpetual markets from Hyperliquid API using info.meta() and returns a list of market data including name, size_decimals, and max_leverage.
    def list_markets(self) -> list[dict[str, Any]]:
        """List all available perpetual markets."""
        meta = self.info.meta()
        markets = []
        for asset in meta.get("universe", []):
            markets.append({
                "name": asset["name"],
                "size_decimals": asset.get("szDecimals", 0),
                "max_leverage": asset.get("maxLeverage", 1),
            })
        return markets
  • The input schema for list_markets tool - defines that the tool takes no arguments (empty properties and required array).
    Tool(
        name="list_markets",
        description="List all available perpetual futures markets on Hyperliquid",
        inputSchema={"type": "object", "properties": {}, "required": []},
    ),
  • The dispatch case that routes list_markets tool calls to the client.list_markets() method.
    case "list_markets":
        return client.list_markets()
Behavior3/5

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

No annotations provided, so description carries full burden. 'List' implies read-only, non-destructive behavior, but description omits rate limits, caching behavior, or response structure (array of symbols vs. full objects) that would help an agent plan invocation strategy.

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?

Single 9-word sentence with action-first structure. No redundant phrases or boilerplate. Every word earns its place.

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?

Adequate for a zero-parameter discovery tool. While no output schema exists, the description sufficiently conveys the tool's role. Minor gap: does not hint at return format (e.g., 'returns market symbols') which would help agent interpret results without invoking.

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 present, meeting the baseline score of 4 per rubric. Description correctly implies no filtering is available (returns 'all' markets), which aligns with the empty 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?

Clear specific verb 'List' with explicit resource 'perpetual futures markets' and scope 'all available on Hyperliquid'. Distinguishes from sibling get_market_info by implying bulk retrieval vs. specific details, and clearly separates from trading actions like place_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides implied usage context (market discovery/initialization) but lacks explicit when-to-use guidance or comparison with get_market_info. Does not clarify whether to use this for trading preparation versus runtime market monitoring.

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/samklein952-hub/hyperliquid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server