Skip to main content
Glama

Get prices

get_prices
Read-onlyIdempotent

Current mid prices for Hyperliquid native perps, spot assets and HIP-3 builder-DEX perps. Spot pairs are resolved to BASE/QUOTE display names (e.g. HYPE/USDC), with data.spot_pairs mapping each back to its native HL pair id (e.g. @107 — needed for raw HL interactions like spot order asset indices). HIP-3 perps are keyed by their dex-prefixed symbol (e.g. xyz:TSLA); data.hip3.failed_dexes lists any DEX whose prices could not be read, and a requested symbol on such a DEX is listed in unavailable_symbols (price unknown right now), not missing_symbols (no such symbol). WITHOUT symbols this returns ~850 entries — prefer scan_markets for discovery and pass symbols here for targeted lookups (perp symbols like BTC, spot pairs like HYPE/USDC, or HIP-3 symbols like xyz:TSLA). A bare ticker with no native market (e.g. GOOGL) resolves to its listing: the price is keyed by the listing (xyz:GOOGL) and data.resolved_symbols maps GOOGL to it. A ticker listed on more than one DEX is not priced; data.ambiguous_symbols lists its candidates so you can ask again with one of them. (Requires api:read.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNosymbols to return, as an array (['BTC','HYPE']) or a comma-separated string ('BTC,ETH,HYPE'); omit for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the ~850-entry bulk response, the api:read permission requirement, and the precise distinction between unavailable_symbols (DEX read failure) and missing_symbols (no such symbol). That failure-mode disclosure is exactly the kind of behavior an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with scope, then behavior, then the discovery-vs-lookup routing — every sentence carries information. It is dense to the point of being crowded, with several parenthetical asides and example symbols that could be trimmed without losing meaning.

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?

With no output schema, the description does the work of explaining the response envelope fields (data.spot_pairs, data.hip3.failed_dexes, data.resolved_symbols, data.ambiguous_symbols, unavailable_symbols), which is unusually thorough. The overall top-level shape of the payload is still left implicit, so it is not fully complete.

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?

Schema coverage is 100%, so the array-vs-comma-string format is already documented; the description goes further by giving the accepted symbol taxonomies (perp tickers like BTC, spot pairs like HYPE/USDC, HIP-3 like xyz:TSLA) and the resolution behavior for bare tickers. It stops short of stating the max of 100 symbols, which only the schema carries.

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?

States a specific verb and resource ("Current mid prices") and enumerates exactly which market families are covered: Hyperliquid native perps, spot assets, and HIP-3 builder-DEX perps. It also distinguishes itself from scan_markets by positioning itself as targeted lookup rather than discovery.

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

Usage Guidelines5/5

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

Explicitly says "WITHOUT `symbols` this returns ~850 entries — prefer scan_markets for discovery and pass `symbols` here for targeted lookups", naming the alternative and the condition that selects it. It also tells the agent how to recover from ambiguity (retry with one of data.ambiguous_symbols).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources