Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

market_orderbook

Retrieve the order book bid and ask depth for any trading pair on Hyperliquid. Analyze liquidity, spread, and support/resistance levels.

Instructions

Get the order book (bid/ask depth) for any trading pair on Hyperliquid. Shows price levels and sizes on both sides. Essential for understanding liquidity, spread, and potential support/resistance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
symbolYesTrading pair symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN format (e.g. xyz:SILVER, km:OIL, cash:TSLA)
depthNoNumber of price levels on each side

Implementation Reference

  • src/index.ts:30-51 (registration)
    Free-tier tool registration: market_orderbook is listed as a free tool (no API key needed)
    const FREE_TIER_TOOLS = new Set([
      'pulse_global_stats',
      'pulse_market_overview',
      'list_markets',
      'market_price',
      'market_orderbook',
      'pulse_most_traded_coins',
      'live_long_short_ratio',
    ]);
    
    const TOTAL_TOOL_COUNT = 43;
    
    if (!API_KEY) {
      console.error(
        `WARNING: COINVERSAA_API_KEY not set. Only free-tier tools will be available (${FREE_TIER_TOOLS.size} of ${TOTAL_TOOL_COUNT}). Get a key at https://coinversa.ai/developers`
      );
    }
    
    function shouldRegister(toolName: string): boolean {
      if (API_KEY) return true;
      return FREE_TIER_TOOLS.has(toolName);
    }
  • Tool schema/registration: defines input schema (useToonFormat, symbol, depth) for market_orderbook
    if (shouldRegister("market_orderbook")) server.registerTool(
      "market_orderbook",
      {
        description: "Get the order book (bid/ask depth) for any trading pair on Hyperliquid. Shows price levels and sizes on both sides. Essential for understanding liquidity, spread, and potential support/resistance.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          symbol: z.string().min(1).max(20).describe("Trading pair symbol (e.g. BTC, ETH, SOL). For builder dex markets use prefix:COIN format (e.g. xyz:SILVER, km:OIL, cash:TSLA)"),
          depth: z.number().min(1).max(50).default(10).describe("Number of price levels on each side"),
        },
      },
  • Handler function: calls API endpoint /market/orderbook/{normalized_symbol} with depth parameter, returns toolResult
      async ({ useToonFormat, symbol, depth }) =>
        toolResult(await callAPI(useToonFormat, `/market/orderbook/${normalizeCoin(symbol)}`, { depth: String(depth) }))
    );
  • Helper function: normalizes coin/symbol string used by market_orderbook handler (e.g. 'btc' → 'BTC', 'xyz:silver' → 'xyz:SILVER')
    function normalizeCoin(raw: string): string {
      const idx = raw.indexOf(':');
      if (idx !== -1) {
        // Builder dex format — keep prefix lowercase, uppercase the coin
        return raw.slice(0, idx).toLowerCase() + ':' + raw.slice(idx + 1).toUpperCase();
      }
      return raw.toUpperCase();
    }
    
    // ─── API Helper (with timeout + retries + friendly errors) ─
Behavior3/5

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

With no annotations provided, the description carries the full burden. It states the tool shows price levels and sizes on both sides, but does not disclose behavioral traits such as read-only nature, rate limits, or response structure. The mention of format options (toon vs JSON) via parameters adds some transparency.

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 extremely concise with two sentences. The first defines the action, the second explains the value. Every word is purposeful, with no redundancy or filler.

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 complexity of an order book tool and no output schema, the description provides a high-level understanding of return values (price levels and sizes). It could be more detailed about the exact structure, but the parameter 'useToonFormat' hints at format variations, making it reasonably complete for an AI agent.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description does not add additional meaning beyond what the parameter descriptions already provide (symbol, depth, useToonFormat). It reinforces the purpose but does not clarify parameter semantics further.

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 tool retrieves the order book for any trading pair on Hyperliquid, specifying it shows bid/ask depth with price levels and sizes. This distinguishes it from sibling tools like market_price or live_liquidation_heatmap by focusing specifically on order book data.

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 explains the tool is essential for understanding liquidity, spread, and support/resistance, giving context for when to use it. However, it does not explicitly mention when not to use it or compare it to alternative tools like market_price or market_positions.

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/Coinversaa/mcp-server'

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