Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_expected_move

Calculate ATR(14)-based 68% and 95% price ranges in USDC around the current Hyperliquid perpetual price for 4h, 1d, or 1w to set targets and stops.

Instructions

Use when the user asks how far a coin may move, or where to put targets and stops. Returns ATR(14)-based 68% and 95% price ranges in USDC around the current price on Hyperliquid perpetuals for the next 4h, 1d or 1w. A statistical range, not a forecast. Ex: symbol=BTC, period=1w 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_expected_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo1d
symbolNoBTC

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?

With no annotations, the description carries the burden and does well: it discloses the data source and model (ATR(14)), the confidence bands (68%/95%), quote currency (USDC), venue (Hyperliquid perpetuals), supported horizons, the non-forecast framing, and even the per-call cost ($0.003 USDC). It omits failure behavior for unsupported symbols and any auth/pricing-tier caveats.

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 compact sentences: trigger first, then what is returned, then a disambiguation caveat, then a concrete example and cost. Nothing is redundant and the most decision-relevant information is front-loaded.

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?

No output schema exists, yet the return is described precisely (68%/95% USDC ranges around current price per horizon), and cost, venue, and the statistical limitation are all covered. Nothing an agent needs in order to call this correctly is missing.

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% and the schema declares no enums, so the description must compensate. It does so substantially by enumerating the allowed periods (4h, 1d, 1w) and giving a worked example (symbol=BTC, period=1w), implicitly defining symbol as a coin ticker; it stops short of stating whether case or alternate symbol formats are accepted.

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 method: 'ATR(14)-based 68% and 95% price ranges in USDC around the current price on Hyperliquid perpetuals' for 4h/1d/1w. An agent can distinguish this from generic volatility or price tools 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?

Gives an explicit trigger ('Use when the user asks how far a coin may move, or where to put targets and stops') and a caveat ('A statistical range, not a forecast'). It does not name when-not-to-use or point to an alternative sibling, which keeps it below a 5.

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