Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_price

Fetches the current price of one coin on Hyperliquid perpetuals in USDC, including mark or order-book mid price, 24h change percentage, and 24h notional volume.

Instructions

Use when the user asks the current price of one coin. Returns the mark price (or order-book mid with price_type=mid) on Hyperliquid perpetuals in USDC, 24h change % and 24h notional volume; high/low are null. For several coins use get_prices. Ex: symbol=ETH Costs $0.005 USDC per call.

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_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC
price_typeNomark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does well: it discloses the return fields (mark price, 24h change %, 24h notional volume), notes high/low are null, identifies the venue (Hyperliquid perpetuals, USDC), and even states the per-call cost. It stops short of auth requirements or rate limits, which is the only material omission.

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?

Four compact sentences with the trigger front-loaded and the alternative and cost appended in priority order. The return-value clause is semicolon-dense and slightly awkward, but every sentence carries information an agent needs.

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 annotations, no output schema, and 0% param coverage, the description covers the trigger, the alternative, the return payload, the venue, and the cost — enough to call it correctly. Missing auth/rate-limit context and the full set of price_type values keep it just short of 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 0%, so the description must compensate and largely does: it explains the price_type=mid alternative to the default mark, and gives a concrete symbol example (symbol=ETH). It doesn't enumerate defaults explicitly or say what other price_type values exist, leaving a small gap.

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 price of one coin') and names the sibling it is not ('For several coins use get_prices'). The scope — single coin, Hyperliquid perpetuals, USDC — is unambiguous without opening the schema.

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?

Opens with an explicit trigger ('Use when the user asks the current price of one coin') and routes multi-coin requests to get_prices. The only minor gap is that it doesn't contrast with analytical siblings like get_expected_move, but the single-vs-multi split is fully stated.

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