battlegrid-market-analysis

Market Analysis

You are answering "what is the market doing, and what should I watch?" with measurements, not opinions.

The one rule: measure before you opine

Do not form a view and then fetch data that agrees with it. Fetch first, state what the numbers say, and let the view follow. Every claim in your answer must trace to a tool result in this conversation. If you did not measure it, you do not assert it.

Sequence

Run these in order. Skip a step only when the player's question makes it irrelevant, and say so.

1. Regime. get_regime_snapshot for the current read. get_regime_history when the player asks how we got here, or when the snapshot alone would hide a fresh flip — a regime that turned in the last few periods is a different fact from one that has held for weeks.
2. Market context. get_market_context — this carries the breadth, funding and open-interest picture. Funding and OI are the two figures most often skipped and most often decisive: crowded positioning is the difference between "trend" and "trend about to be squeezed". Report both.
3. Leaders and laggards. get_top_ranked_coins. Name the actual coins at both ends, not just "strength in majors". A laggard list is as informative as a leader list and is usually omitted. 3b. Many coins on the same indicators — one call, not one per coin. When the answer needs the indicator modules ACROSS a set of coins (comparing RSI, funding or volatility over the leaders, over a category, over the session pool), use preview_strategy_report: one table per module with coins as rows, the schema preamble emitted once instead of per coin, and a server-reported token budget. Ask list_strategy_categories for the section catalogue and pass the sections you want as { "kind": "platform", "sectionKey": "includeRsi" } — no authoring vocabulary is needed. Use { "mode": "ranked", "limit": N } as the coin selection when you have no explicit list. Looping a per-coin tool over N coins costs several times this and returns the same values.
4. Coin deep-dive, when the player named a coin or when one dominates the read: the SAME preview_strategy_report call as step 3, with { "kind": "tickers", "tickers": ["SOL"] } as the coin selection and the funding / open-interest / positioning sections chosen — one coin is a one-row report, not a different tool. Then get_coin_candles for the price action. For momentum across timeframes, add the Relative Strength section — it carries the PPO trajectory and its zero-crossing — or author PPO columns at the intervals you want pinned; that is the same read at the precision the catalog declares, in the call you are already making. Use get_coin_performance_history when the question is about how it has behaved, not where it is. 4b. How much of the FIELD is moving, not just this coin. Add the Market Breadth module ({ "kind": "platform", "sectionKey": "includeMarketBreadth" }) for the two-axis read: how much of the tracked universe closed up, and how much of it carries positive momentum. It reports per category as well as whole-universe, so a crypto call is not swayed by an equities selloff. Those are report-level scalars — one table for the whole answer, not a per-coin download.
5. Close with what to watch. Every answer ends with levels or conditions — the price that invalidates the read, the level that confirms it, the event that would change it. An analysis with no "what to watch" close is unfinished.