Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

is_this_a_dip

Checks if a price drop is a real dip or noise by measuring the drop from the 14-day high against 14-day ATR and returning a daily-candle verdict.

Instructions

Use when the user asks if a drop is a real dip or noise. Returns is_dip, drop % from the 14-day high, 14-day ATR %, drop/ATR and a verdict on daily candles. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=SOL 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_a_dip"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolNoBTC

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, the description carries the full burden and does well: it discloses the computed timeframes, the daily-candle basis, the asset universe restriction, and a per-call price of $0.003 USDC. The phrase 'others unpaid' is ambiguous (it likely means unsupported/not covered) and there is no statement of what happens when an out-of-universe symbol is passed, which is the main remaining gap for a paid tool.

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?

Front-loaded with the trigger condition, then outputs, then scope, then an example and cost — a sensible order with almost no filler. The clipped fragment 'others unpaid' costs clarity for the sake of brevity and should be a full clause.

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 correctly enumerates the returned fields and adds the cost and universe constraints an agent needs before calling. It is nearly complete for a one-parameter tool, lacking only error behavior for unsupported symbols and a clearer definition of what the 'verdict' values can be.

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% and the single 'symbol' parameter is documented only by a title and default of BTC. The description partially compensates by showing 'symbol=SOL' and constraining valid values to top-50 Hyperliquid perpetuals, but it never states the expected format or case sensitivity, so an agent still has to guess at the input contract.

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 specific question it answers ('is a drop a real dip or noise') plus the exact signal set (drop % from 14-day high, 14-day ATR %, drop/ATR, verdict on daily candles). This clearly separates it from siblings like is_this_a_breakout or is_this_oversold, which address different market questions.

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 ('when the user asks if a drop is a real dip or noise') and an explicit coverage boundary: top 50 Hyperliquid perpetuals by 30-day volume, with a pointer to get_supported_assets for the list. It stops short of naming when-not-to-use alternatives such as is_this_support or is_price_extended, so the agent must infer the routing for adjacent questions.

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