Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

is_this_support

Determine if a crypto price level is genuine support by analyzing 0.5% touches, recency, and bounce quality across 90 daily candles; get a clear verdict.

Instructions

Use when the user asks if a price level is real support. Returns touches within 0.5% over 90 daily candles, recency, bounce quality, verdict. Level in USDC, required. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=ETH, level=3000 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_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does substantial work: it discloses the output fields, the 90-day/0.5% methodology, the top-50-perp coverage limit, and a per-call price of $0.003 USDC. The phrase 'others unpaid' is ambiguous -- it is unclear whether unsupported symbols error out or return a different paid result -- and failure behavior or rate limits are not described.

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 the return shape, then constraints, then an example and price -- a sensible priority order with no filler. The telegraphic fragments ('Level in USDC, required', 'others unpaid') are compact but slightly at the cost of clarity on the payment/coverage edge case.

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 paid, unannotated, no-output-schema tool, this description covers what is needed to call it correctly: trigger, required unit, asset universe, expected response fields, example, and cost. The only real gap is the meaning of 'others unpaid' for out-of-universe symbols, which leaves an agent unsure what happens on a bad call.

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%, so the description must compensate, and it mostly does: 'level' is marked required and specified as being in USDC, and 'symbol' is illustrated with the example symbol=ETH, level=3000 plus the top-50-perp constraint. It does not mention that symbol defaults to BTC, which the schema carries but an agent skimming the description might miss.

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 verb and resource -- answering whether a price level is 'real support' -- and immediately defines the mechanism (touch count within 0.5% over 90 daily candles) plus the returned fields (touches, recency, bounce quality, verdict). This clearly separates it from siblings like is_this_a_dip or is_this_a_breakout, which ask different questions about price action.

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 price level is real support' gives a concrete trigger, and the coverage restriction routes the agent to get_supported_assets before calling. It stops short of explicitly stating when NOT to use it (e.g., for resistance levels or intraday timeframes) or naming a sibling alternative, so it is clear but not fully exclusive.

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