Skip to main content
Glama

Surf Hyperliquid

surf_hyperliquid
Read-only

Fetch Hyperliquid portfolio, market, and trading data. Track account positions, fills, orders, and leaderboard performance.

Instructions

Use this when the user needs hyperliquid data from Surf.

Commands: account - Account Portfolio params: address* (string) candles - Market Candles params: symbol* (string), interval (string), from* (string), to* (string) fills - Fills params: address* (string), from (string), to (string), to_ms (integer), to_fill_id (string), order (string) [desc, asc], cursor (string), symbol (string), limit (integer) leaderboard - Trader Leaderboard params: time_range (string) [1d, 7d, 30d, 90d, all], sort_by (string) [total_pnl, win_rate, volume_traded], min_trades (integer), min_days_active (integer), min_account_age_days (integer), min_human_score (integer), dex (string), limit (integer), offset (integer) orders - Open & Recent Orders params: address* (string), open_limit (integer), historical_limit (integer) performance - Trading Performance params: address* (string), dex (string) positions - Open Positions params: address* (string), dex (string) trades - Closed Trades params: address* (string), symbol (string), direction (string) [long, short], dex (string), from (string), to (string), cursor (string), limit (integer) trades-aggregate - Closed Trades Aggregate params: address* (string), group_by (string) [day, symbol, direction, size_bucket, hold_bucket], from (string), to (string), dex (string), fill_gaps (boolean) trade-context - Closed Trade Funding and Leverage params: address* (string), symbol* (string), direction* (string) [long, short], open_time* (integer), close_time* (integer)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
commandYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read behavior is known. The description adds a comprehensive command reference but does not disclose additional behavioral traits such as data freshness, pagination handling, authentication requirements, or any potential rate limits. It does not contradict the annotations.

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 efficiently structured as a command list with each line showing the command name and its parameters. The purpose sentence is front-loaded, and there is no filler. Despite its length, every entry earns its place by providing essential invocation details for the tool's many subcommands.

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?

The description covers all ten commands and their parameter lists, providing a complete map of the tool's capabilities. However, it does not explicitly state how the top-level params object should be populated for each command, nor does it describe the return value structure. Since there is no output schema, a brief note on response format would improve completeness, but the command names and parameter lists make the intended calls reasonably clear.

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

Parameters5/5

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

The input schema only defines a command enum and a free-form params object, providing zero documentation for nested parameters. The description compensates fully by listing every command's parameters, marking required ones with an asterisk, and specifying enums for many fields (e.g., interval, order, time_range). It also disambiguates formats (e.g., to_ms integer) and optionality, adding substantial meaning beyond 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 sentence clearly states 'Use this when the user needs hyperliquid data from Surf', specifying the exact resource and action. It then enumerates all available commands, making the tool's scope unmistakable and distinguishing it from sibling tools that target other data domains (e.g., surf_dex, surf_token).

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?

The description gives a clear 'Use this when...' context, and the command list provides intra-tool guidance on which command to invoke for specific data needs (e.g., account, candles, trades). However, it does not explicitly mention when not to use this tool or point to alternatives like surf_onchain for other types of data.

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/asksurf-ai/surf-mcp'

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