TraderSpy Technical Analysis

One good read of a chart is three things in order: where price is in its structure (trend and levels), what momentum and volatility are doing, and how the derivatives market is positioned around it. TraderSpy gives all three in at most two calls. Spend the calls well — the user's quota is finite — and quote the numbers, not adjectives.

When to Use

• Use when the user asks about a coin's chart, trend, momentum, support and resistance, or where a level such as the 200 EMA sits.
• Use for "analyse BTC", "how does SOL look", "is X overbought / oversold", "what do the indicators say" or "is this a good entry", even when the user only names a coin.
• Use when the question is whether funding is high or open interest is building, or when the user wants price or candle data.
• For scanning many coins by conditions use @traderspy-market-screener; for whale positions use @traderspy-smart-money.

Tools

Symbols are Binance Futures names: BTCUSDT, SOLUSDT, 1000PEPEUSDT (1000x-prefixed small caps), and tokenized equities/ETFs such as AAPLUSDT or SPYUSDT. Append USDT to a bare coin. Hyperliquid-only perps (e.g. HYPE) are tracked under the same naming.

Making the call count

• Multi-timeframe is one quota unit. For any "how does X look" question pass intervals: ["1h","4h","1d"] (or ["15m","1h","4h"] for an intraday user) and get a confluence verdict — never three separate calls.
• Pick indicators for the question. Default rsi, macd, ema, bollinger covers momentum and trend. Add levels + pivots whenever the user cares about entries, targets or "where is support"; atr for stop distance and volatility; adx for trend strength; supertrend for a clean trend state; obv / mfi when volume confirmation matters; ichimoku / keltner only when asked. Eight to ten well-chosen indicators is a full read; all 19 is noise.
• periods lets you honour the user's settings ({"ema":[9,21,55,200],"rsi":7}); an unknown key is rejected, so use the documented names only.
• Add get_derivatives when the question involves "why is it moving", crowding, funding, open interest, leverage, liquidations, or when the user is about to lean on a directional call — candles cannot see positioning.
• get_candles is for when the user wants the data itself (to chart, export or compute something custom). Do not fetch candles to eyeball indicators the technicals tool already computes.

Reading the response

Shape. One timeframe → top-level indicators + summary. Several → timeframes[] (each with interval, price, candles, indicators, summary) plus confluence { aligned, bias, byInterval }; the top-level interval/price then name the first timeframe only. settings echoes what was computed; warnings[] lists anything that was thinned or missing.

Every indicator carries value, previous, direction (rising / falling / flat) and a short series (oldest → newest), plus its own fields — zone on RSI/Stochastic/CCI/MFI/Williams, crossover on MACD/Stochastic, stack/pricePosition on EMA, ±DI and strength on ADX, trend/flipped/barsSinceFlip on SuperTrend, divergence on RSI/MACD/OBV. { value: null, reason: "insufficient_data" } means the tape is too short for that period — say so, do not substitute.

summary is the spine of the read. bias (bullish / bearish / neutral) is computed from a FIXED set (RSI 14, MACD, EMA 20/50/200, ADX 14, ATR 14, BB 20/2, volume 20) regardless of what you requested, so it is comparable between calls; score is its internal vote (|score| ≥ 30 sets a bias). trend (direction, strength, emaStack, priceVsEma200), momentum (rsiZone, macdState), volatility (atrPct, atrPercentile 0–100, squeeze, state), volume.ratioVsAverage, patterns[]

…