Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

market_price

Get current mark price for any trading pair on Hyperliquid. Supports standard crypto symbols and builder dex market formats like xyz:SILVER.

Instructions

Get current mark price for any trading pair on Hyperliquid. Use standard symbols (BTC, ETH, SOL) or builder dex format (xyz:SILVER, km:OIL, cash:TSLA).

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)

Implementation Reference

  • src/index.ts:30-38 (registration)
    market_price is listed as a free-tier tool, meaning it's available without an API key.
    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',
    ]);
  • Input schema for market_price: accepts useToonFormat (boolean) and symbol (string, 1-20 chars) for the trading pair.
      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)"),
      },
    },
  • Handler for market_price: calls the API endpoint /market/price/{symbol} after normalizing the coin symbol (uppercasing and handling builder dex prefix format).
      async ({ useToonFormat, symbol }) => toolResult(await callAPI(useToonFormat, `/market/price/${normalizeCoin(symbol)}`))
    );
  • src/index.ts:455-465 (registration)
    Registration of the market_price tool on the MCP server, with description, input schema, and handler function.
    if (shouldRegister("market_price")) server.registerTool(
      "market_price",
      {
        description: "Get current mark price for any trading pair on Hyperliquid. Use standard symbols (BTC, ETH, SOL) or builder dex format (xyz:SILVER, km:OIL, cash:TSLA).",
        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)"),
        },
      },
      async ({ useToonFormat, symbol }) => toolResult(await callAPI(useToonFormat, `/market/price/${normalizeCoin(symbol)}`))
    );
Behavior3/5

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

No annotations are provided, so the description must disclose behaviors. It implies a read-only operation (getting a price) and mentions supported symbol formats. However, it does not state that it is non-destructive or any other behavioral traits.

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 only two sentences with no unnecessary words. It is front-loaded with the action and resource. Highly concise.

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?

No output schema, so description should indicate return type. It only says 'Get current mark price' but does not specify the format (e.g., number, object). For a simple tool, it may be adequate, but could be improved.

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 coverage is 100%, so baseline is 3. The description adds detail on symbol format (examples) but does not explain 'useToonFormat' (compact format) beyond what the schema already provides. Thus minimal added value.

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 current mark price'), the resource ('any trading pair on Hyperliquid'), and the supported formats. It distinguishes from sibling tools like market_orderbook or market_positions by focusing on mark price.

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 provides guidance on acceptable symbol formats (standard and builder dex). It does not explicitly state when not to use or list alternatives, but the context of siblings makes the purpose clear.

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