Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_compression_alert

Detect whether a Hyperliquid perpetual is in a volatility squeeze before a breakout, returning squeeze level and Bollinger width percentile for the chosen symbol and timeframe.

Instructions

Use when the user asks whether a coin is in a volatility squeeze before a breakout. Returns is_squeeze, level (extreme, strong, moderate, none), Bollinger width and its percentile on 1h, 4h or 1d candles of Hyperliquid perpetuals. Setup, not direction. Ex: symbol=BTC, timeframe=1d 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_compression_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC
timeframeNo4h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full disclosure burden; it does well by stating concrete return fields, supported timeframes (1h/4h/1d), the underlying data source (Hyperliquid perpetuals) and a per-call price of $0.003 USDC. It does not state whether the call is read-only, what happens for an unsupported symbol, or whether the cost is charged on failure — gaps that matter somewhat given zero annotation coverage.

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-loads the trigger, then returns, then the interpretive caveat, then an example and the cost — every sentence adds distinct information and nothing is padded or repeated.

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 two-parameter read tool with no output schema and no annotations, the description covers trigger, return shape, timeframe options, data source, and cost. Missing only edge-case behavior (invalid symbol/timeframe handling) and guidance on choosing among the three timeframes, which are minor for this complexity.

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 0%, so only the description adds meaning: it supplies a usage example (symbol=BTC, timeframe=1d) and enumerates the legal timeframe values (1h, 4h, 1d), which is genuinely useful beyond the bare string schema. It still says nothing about which symbols are valid or the units/interpretation of the percentile, leaving half the parameter surface under-specified.

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+resource: detects whether a coin is in a volatility squeeze ahead of a breakout, and enumerates the returned fields (is_squeeze, level with its four values, Bollinger width and percentile). The phrase 'Setup, not direction' distinguishes it conceptually from breakout/volatility siblings, though no sibling is named explicitly.

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 whether a coin is in a volatility squeeze before a breakout') and adds the clarifying exclusion that it describes a setup rather than directional bias. No alternative tool is named for the adjacent breakout question, so routing against siblings like is_this_a_breakout is left to inference.

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