Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

is_this_oversold

Determine whether a Hyperliquid perpetual is oversold using RSI(14) on 1h, 4h, and 1d timeframes plus a weighted verdict; treat the result as context, not a standalone buy signal.

Instructions

Use when the user asks if a coin is oversold. Returns is_oversold, RSI(14) on 1h, 4h and 1d, a weighted RSI (20/30/50%) and a verdict; not a buy signal alone. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=BTC 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_this_oversold"
  }
}

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 provided, the description carries the full burden and does a solid job: it discloses the per-call price ($0.003 USDC), the coverage limitation (top 50 perps, 'others unpaid'), and a caution that the verdict is 'not a buy signal alone.' It leaves ambiguity around what happens when a symbol falls outside the supported set (error, charge, or fallback).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger is front-loaded, followed by return values, coverage limits, and cost in a compact block with no filler sentences. The telegraphic phrasing ('others unpaid', bracketed weight percentages) is dense but every clause carries 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?

For a one-parameter tool with no output schema, listing the returned fields, the supported universe, and the price covers what an agent needs before calling. The only meaningful omission is failure behavior for unsupported symbols and the exact symbol format accepted.

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 description coverage is 0% for the single symbol parameter, so the description must compensate, and it does reasonably: it names the enumeration source (get_supported_assets) and supplies a concrete example (symbol=BTC). It could be tighter on expected symbol format (e.g., 'BTC' vs 'BTCUSDT'), which is the main residual gap.

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 verb and question ('is a coin oversold') and enumerates exactly what comes back (is_oversold flag, RSI on 1h/4h/1d, weighted RSI, verdict), so the tool is immediately distinguishable from sibling indicator tools. It does not explicitly name the nearest siblings (is_this_a_dip, is_this_support), leaving the agent to infer the boundary from semantics alone.

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 an explicit trigger ('Use when the user asks if a coin is oversold') plus important usage constraints: the universe is limited to the top 50 Hyperliquid perpetuals by 30-day volume, with a pointer to get_supported_assets for the list, and a stated cost. It stops short of stating when NOT to use it versus the dip/support siblings.

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