Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_chop_detection

Detect whether a Hyperliquid perpetual is trending or stuck in a range on 1h, 4h, or 1d candles; get chop level, ADX, directional indicators, and a trend verdict for any symbol.

Instructions

Use when the user asks whether a coin is trending or stuck in a range. Returns is_chop, chop level, ADX, +DI/-DI, trend direction and a verdict on 1h, 4h or 1d candles of Hyperliquid perpetuals. Any active market. Ex: symbol=SOL, timeframe=4h 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_chop_detection"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC
timeframeNo4h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 burden and does well: it discloses the data source (Hyperliquid perpetuals), the market scope (any active market), the timeframe domain, the fact this is a read-style analytical result, and a per-call cost of $0.003 USDC, which matters for an agent budgeting calls. It does not cover failure modes for invalid symbols or unsupported timeframes, which is the only notable gap.

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?

Four short sentences in a deliberate order: trigger, payload, scope, concrete example, cost. Nothing is redundant, and the usage signal is front-loaded where an agent will read it first.

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?

This is a simple two-parameter read tool, and the description covers the missing pieces an agent needs: what the returned values mean, which timeframes exist, which markets are supported, and what a call costs. With no output schema present, the enumeration of return fields is the right compensating detail.

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 description coverage is 0%, so the description must compensate, and it partly does: it names the valid timeframes (1h, 4h, 1d) and gives a concrete example (symbol=SOL, timeframe=4h) plus the statement that any active market is supported. It never states the defaults documented in the schema (BTC, 4h) or the symbol format, so meaning is added but not fully.

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?

The description uses a specific verb-and-resource framing: it detects whether a coin is trending or range-bound, and enumerates the exact metrics returned (is_chop, chop level, ADX, +DI/-DI, trend direction, verdict). That is enough to separate it from siblings like get_market_regime or is_this_a_breakout without opening a schema, though it never explicitly names those alternatives.

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?

The opening sentence gives a clear trigger condition ("user asks whether a coin is trending or stuck in a range"), which is a real when-to-use statement rather than a restatement of the name. It stops short of exclusions or explicit routing to a competing sibling, so an agent must infer the boundary with regime/breakout tools.

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