Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

is_this_a_breakout

Check whether a price-level break is confirmed or a fakeout using volume and 1-hour closes; returns confirmation status, fakeout odds, and a verdict.

Instructions

Use when the user asks if a break of a price level is real or a fakeout. Returns is_confirmed, fakeout odds, verdict from volume and 1h closes past the level (USDC, required). Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=BTC, level=100000 Costs $0.003 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "level": "<level>"
    },
    "name": "is_this_a_breakout"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes
symbolNoBTC
directionNoup

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 substantial work: it discloses the signal inputs (volume and 1h closes past the level), the return fields, the asset universe restriction, and a per-call price of $0.003 USDC. What remains ambiguous is the phrase 'others unpaid' — it does not say whether an out-of-universe symbol errors or returns a paywall message — and nothing is said about latency.

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?

Four short clauses, front-loaded with the use case and followed by output, scope, cost, and an example — no wasted sentences. The tradeoff is a telegraphic style ('others unpaid') that reads as compressed rather than clear in one spot.

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?

With no output schema, the description still enumerates the returned fields and explains the evidence behind them, and it covers cost, payment currency, and universe limits for a paid tool. It is only incomplete on `direction` semantics and on failure behavior for unsupported symbols.

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 supply all parameter meaning. It gives a worked example (symbol=BTC, level=100000) that anchors `level` as a price and confirms `symbol`, but the third parameter `direction` is never mentioned or explained, even though it has no enum and defaults to 'up' — a real gap that could produce wrong-direction calls.

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?

The description names a specific question the tool answers — whether a break of a price level is real or a fakeout — and enumerates the concrete outputs (is_confirmed, fakeout odds, verdict). That is enough to separate it from siblings like is_this_support or is_this_dip without opening any 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?

The opening clause 'Use when the user asks if a break of a price level is real or a fakeout' is an explicit triggering condition, and the coverage note ('top 50 Hyperliquid perpetuals by 30-day volume only, see get_supported_assets') tells the agent when the tool cannot serve a request. It stops short of naming an alternative tool for the case where the level is support rather than a breakout, so no true exclusion against siblings.

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