Skip to main content
Glama
derkcc

market-depth-lab-mcp

by derkcc

List top position holders in a Hyperliquid market

hyperliquid_list_top_position_holders
Read-onlyIdempotent

Retrieve the largest current positions for a canonical market from a monitored cohort of public addresses, sorted by notional, PnL, or leverage.

Instructions

List the largest current positions for one canonical market inside Market Depth Lab's monitored public-address cohort. Rankings are cohort-relative and the index retains only the published top positions per market.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideNoall
limitNo
marketYesCanonical market, for example BTC or xyz:NVDA.
offsetNo
sort_byNoposition_notional
address_queryNo
min_position_notional_usdNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesStructured tool result.
Behavior4/5

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

The description adds behavioral context beyond the annotations (readOnlyHint, openWorldHint, idempotentHint): it notes that rankings are 'cohort-relative' and that the index 'retains only the published top positions per market'. This helps the agent understand limitations.

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?

Two sentences, front-loaded with the core purpose, no fluff or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 7 parameters and limited schema descriptions, the description covers the core function adequately but lacks details on filtering and sorting options. The presence of an output schema reduces the need to explain return values, but more parameter context would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14% (only 'market' has a description). The description does not describe any parameters, failing to compensate for the low coverage. Parameters like side, limit, offset, and sort_by are left to be inferred from their names.

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 description uses a specific verb ('List') and resource ('largest current positions'), scoped to 'one canonical market inside Market Depth Lab's monitored public-address cohort'. This clearly distinguishes it from sibling tools like list_active_hyperliquid_twaps or hyperliquid_list_funding_rates.

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?

No explicit guidance on when to use this tool versus alternatives. The usage is implied by the name and description, but no exclusions or comparative advice is provided.

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/derkcc/market-depth-lab-mcp'

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