Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_volatility

Measures how volatile a Hyperliquid perpetual coin has been by returning daily and annualized realized volatility over 7d, 14d, or 30d, plus a low-to-extreme level and today’s UTC range versus open.

Instructions

Use when the user asks how volatile a coin has been. Returns daily and annualized realized volatility % over 7d, 14d or 30d of daily candles on Hyperliquid perpetuals, a low/normal/high/extreme level and today's UTC range vs open. Not implied vol. Ex: symbol=BTC, period=30d Costs $0.010 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_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo7d
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose the data source (Hyperliquid perpetuals), candle granularity, the concrete return fields (daily/annualized vol, low/normal/high/extreme level, today's UTC range vs open), and the $0.010 USDC cost. It omits failure behavior, what happens for unsupported symbols or periods, and whether defaults apply, which matters for a paid, unannotated call.

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 returns, then a compact example, then the price. Every sentence adds information; no padding or restatement of the tool name.

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?

For a 2-parameter tool with no output schema or annotations, the description covers purpose, output shape, valid period values, source venue, and cost. The gaps are defaults (period=7d, symbol=BTC) and edge-case behavior, which are minor but would otherwise need schema inspection.

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 it largely does: it enumerates the valid period values (7d/14d/30d) that the schema lacks entirely and gives a worked symbol/period example. Symbol format (ticker like BTC on Hyperliquid) is only implied by the example, and the 7d/BTC defaults go unmentioned.

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 concrete resource and output ('daily and annualized realized volatility % over 7d, 14d or 30d of daily candles on Hyperliquid perpetuals') plus a classification level, and explicitly excludes a confusable neighbor with 'Not implied vol.' An agent can tell exactly what this returns 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 Guidelines4/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 how volatile a coin has been') and rules out the implied-vol interpretation. It does not name an alternative tool for the implied-vol case or state when-not to call it beyond that, so it stops short of full routing guidance.

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