Skip to main content
Glama
Sign In
pathiel

pathiel

by Julian-dev28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_markets

Read-only

Scan and rank Hyperliquid markets by 24h volume, funding, open interest, or mid price, with filters for perps, spot, query, and limit. Returns size decimals and max leverage for order sizing.

Instructions

List many coins at once, one board per call, to scan or rank the market. view=instruments (default): tradable perps and spot, highest 24h volume first, each with max leverage, funding, open interest and mid; query, type and limit narrow this view only. view=mids: every mid price (coins narrows it). view=funding: every coin by hourly funding. view=open_interest: the top 100 by open interest. view=assets: size decimals and max leverage per main-dex perp, for order sizing. limit defaults to 50 (max 1000). For one coin's full snapshot use get_market instead; for price history use get_candles. Read-only; needs no key. Returns {instruments[], counts, matched} for instruments, {count, mids} for mids, {count, rows[]} for funding and open_interest, and {count, assets[]} for assets; a venue failure returns {error} with isError true.

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

Input Schema

NameRequiredDescriptionDefault
typeNoview=instruments: perps or spot only.
viewNoWhich board to return.instruments
coinsNoview=mids: only these coins.
limitNoview=instruments: most rows to return.
queryNoview=instruments: keep names containing this text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds auth context ('needs no key'), the failure mode ('a venue failure returns {error} with isError true'), the limit default and ceiling (50, max 1000), and the exact response envelope per view. That is meaningful behavioral disclosure beyond the annotation.

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?

Extremely dense with zero filler — every clause carries either a view meaning, a scoping rule, or a routing pointer. It is a single run-on block rather than a structured list, which slightly hurts scanability but the key purpose is front-loaded.

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?

No output schema exists, and the description compensates by describing the return envelope for every view ({instruments[], counts, matched}, {count, mids}, {count, rows[]}, {count, assets[]}). Combined with defaults, bounds, and error behavior, an agent has everything needed to call and interpret it.

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 already 100%, so the baseline is 3; the description adds scoping rules the schema implies but does not fully state (query/type/limit 'narrow this view only', coins applies only to mids) and supplies the limit default of 50 and max of 1000, which the schema lacks entirely. Marginal but real added meaning.

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?

Opens with a concrete verb+resource ('List many coins at once, one board per call') and enumerates the five distinct boards it can return (instruments, mids, funding, open_interest, assets), so an agent immediately knows what data it gets. It also contrasts itself with get_market and get_candles, making selection unambiguous without opening sibling schemas.

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?

Explicit routing: 'For one coin's full snapshot use get_market instead; for price history use get_candles,' plus per-view guidance (assets view 'for order sizing', instruments 'to scan or rank the market'). It also states which parameters apply to which view, effectively giving when-to-use conditions for each mode.

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

Deploy Server

Other Tools