Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_prices

Fetch USDC mark or mid prices, 24h change, and 24h volume for up to 20 crypto symbols on Hyperliquid perpetuals; use for portfolios or single coins, unknown symbols are skipped.

Instructions

Use when the user asks the prices of several coins or a portfolio. Returns, keyed by symbol (max 20), the mark or mid price on Hyperliquid perpetuals in USDC, 24h change % and 24h notional volume; unknown symbols are skipped. Works with one symbol too. Ex: symbols=BTC,ETH,SOL Costs $0.003 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_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoBTC,ETH
price_typeNomark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does much of it: it discloses the 20-symbol cap, that unknown symbols are silently skipped, the quote currency (USDC), the returned fields, and a per-call cost of $0.003 USDC. It omits any error behavior when all symbols are unknown and any rate-limit context beyond price.

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?

Front-loaded with the trigger, then return shape, then limits and exceptions, then a concrete example and cost. Every sentence adds information an agent would otherwise have to guess at, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema and no annotations, the description covers trigger, return fields, cap, skip behavior, example syntax and cost — everything needed to invoke it correctly and anticipate the response shape.

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 description coverage is 0%, so the description must compensate; it does so by showing the format via 'Ex: symbols=BTC,ETH,SOL' and by stating the price_type options ('mark or mid price'). It never names the parameters, gives the default values (BTC,ETH / mark), or specifies the delimiter explicitly beyond the example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Returns ... the mark or mid price on Hyperliquid perpetuals in USDC') plus the scope (max 20 symbols, keyed by symbol) and the extra fields returned. It does not name or contrast with the obvious singular sibling get_price, so the batch-vs-single boundary is only hinted at by 'Works with one symbol too'.

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?

'Use when the user asks the prices of several coins or a portfolio' is a clear, concrete trigger condition. There is no when-not guidance or pointer to an alternative tool, so an agent deciding between this and get_price for a single symbol must infer it.

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