Skip to main content
Glama

waiaas_hl_get_spot_markets

Retrieve the list of available spot markets on Hyperliquid, including trading pairs and token information.

Instructions

Get Hyperliquid spot market list (trading pairs, token info).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'waiaas_hl_get_spot_markets' tool. It makes a GET request to '/v1/hyperliquid/spot/markets' via the apiClient and returns the result. No parameters are required.
    // hl_get_spot_markets
    server.tool(
      'waiaas_hl_get_spot_markets',
      'Get Hyperliquid spot market list (trading pairs, token info).',
      {},
      async () => {
        const result = await apiClient.get('/v1/hyperliquid/spot/markets');
        return toToolResult(result);
      },
    );
  • Empty input schema (no parameters) for the spot markets tool, defined inline as an empty object literal.
    {},
  • The 'registerHyperliquidTools' function registration, called from server.ts line 127. It receives the MCP server, apiClient, and walletContext.
    export function registerHyperliquidTools(
      server: McpServer,
  • The call site in createMcpServer that registers all Hyperliquid tools, including the spot markets tool.
    registerHyperliquidTools(server, apiClient, walletContext);
  • The 'toToolResult' helper used by the handler to convert the API response to MCP CallToolResult format.
    export function toToolResult<T>(result: ApiResult<T>): CallToolResult {
Behavior3/5

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

The description implies a read-only operation via 'Get', but does not explicitly state side effects, authentication needs, or rate limits. With no annotations, more detail would be helpful, but the simple nature of the tool keeps it adequate.

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 a single sentence that efficiently conveys the tool's purpose. It is front-loaded with the key action and resource, with no extraneous content.

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?

Given the tool has no parameters and no output schema, the description sufficiently explains the return (trading pairs, token info). It could mention if all markets are included, but overall it is complete for a simple listing tool.

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?

There are no parameters in the input schema, so schema coverage is 100%. The description adds no param info, which is acceptable as none exist. Baseline is set to 4.

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 clearly states the action 'Get' and the resource 'Hyperliquid spot market list', specifying it includes trading pairs and token info. This is distinct from sibling tools like waiaas_hl_get_markets (likely for perpetuals) and waiaas_hl_get_spot_balances.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs alternatives. There is no indication of prerequisites, exclusions, or comparison to siblings like waiaas_hl_get_markets.

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/minhoyoo-iotrust/WAIaaS'

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