Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

is_price_extended

Checks whether a Hyperliquid perpetual's price is stretched far from its moving averages, returning MA20/MA50 distance, Bollinger position, 4h z-score, and an extended-price verdict.

Instructions

Use when the user asks if price is stretched far from its average. Returns distance from MA20 and MA50, Bollinger position, z-score on 4h candles, is_extended and a verdict. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=ETH 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": "is_price_extended"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries real weight and does disclose non-obvious traits: universe restriction to the top 50 perps by volume, that non-eligible symbols are 'unpaid', and a per-call cost of $0.003 USDC. Those are exactly the facts an agent needs before spending money. It does not say whether an ineligible symbol errors or returns a soft signal, which is the remaining 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 compact sentences, front-loaded with the triggering question, then outputs, then eligibility, then cost and an example. No filler; every clause carries calling-relevant information.

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?

There is no output schema, so the description's field list (MA20/MA50 distance, Bollinger position, z-score, is_extended, verdict) is doing necessary work, and cost plus coverage limits are covered. What is missing is failure behavior for out-of-universe symbols and confirmation of the default symbol.

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% for the single 'symbol' parameter, so the description must compensate. It offers an example ('symbol=ETH') showing the expected format, and the top-50 constraint scopes valid values, but it never states that symbol is optional or defaults to BTC, which the schema declares.

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 states a specific trigger ('asks if price is stretched far from its average') and enumerates the outputs (MA20/MA50 distance, Bollinger position, 4h z-score, is_extended, verdict), so the resource is unambiguous. It does not explicitly contrast itself with close siblings such as is_this_oversold or is_this_a_dip, leaving that separation to inference.

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?

It gives a clear use condition ('when the user asks if price is stretched far from its average') plus a hard eligibility constraint: only the top 50 Hyperliquid perps by 30-day volume, with others unpaid. It points to get_supported_assets for the allowlist. It stops short of naming when to prefer a sibling tool instead.

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