EdgeBreak

Primary tool for watchlist-level support and breakdown questions such as 'have any stocks on my watchlist fallen below support?', 'which of my saved stocks broke support?', 'has anything on my watchlist lost support?', 'are any watchlist stocks breaking down?', or 'which watchlist stocks have broken recent structure?'. Checks every saved watchlist ticker against completed EdgeBreak daily chart history. Prefers a genuine published EdgeBreak Launchpad support zone when available; otherwise derives recent price-structure support from existing completed OHLCV. Returns below support, testing support, above support, reclaimed support, or unavailable, and clearly identifies whether support is published or derived. Do not use the plain watchlist action as a substitute for this support/breakdown intent.

check_watchlist_support

Default tool for broad individual-stock EdgeBreak research. Use for requests such as 'what does EdgeBreak think of SGMT?', 'tell me about SGMT', 'analyse SGMT', 'what are you seeing in SGMT?', 'how does SGMT look?', 'is SGMT setting up?' or 'check SGMT'. The default compact response contains the customer-relevant scanner, structure, momentum/volume, off-exchange, PBI and ranking fields needed for a concise assessment. Set detail_level to full only when the user explicitly asks for full technical detail, all indicators, the full record or a detailed technical table. Use get_stock_signal only when the user specifically wants current breakout-scan membership/status. If the user also asks to see the chart, also call show_stock_chart. Present friendly customer language, keep PBI rank distinct from Daily Top 20/Top 6, and never infer buying or selling direction from off-exchange activity alone. Keep the output factual and setup-focused; do not turn EdgeBreak intelligence into a personalised buy/sell recommendation.

get_stock_intelligence

Use only when the user is specifically asking whether one ticker is present in the latest published EdgeBreak breakout scan or wants that ticker's current breakout-signal status/data. Examples include 'is SGMT in today's breakout scan?', 'what is SGMT's current breakout signal?', or 'did SGMT trigger today?'. For broader questions such as 'what does EdgeBreak think of SGMT?', 'analyse SGMT', 'how does SGMT look?', or 'is SGMT setting up?', prefer get_stock_intelligence. For previous EdgeBreak appearances, use get_signal_history. Keep the returned stock data factual and do not turn it into a personalised trade recommendation.

get_stock_signal

Use for custom EdgeBreak scans across the full current published EdgeBreak universe, including combinations that go beyond the smaller in-journey refine menu. Translate natural-language requests into the same Master Scanner filter schema used by the EdgeBreak website. Supports setup type, price, PBI, RSI, resistance distance, structure, volume, moving-average position and recent crosses, OBV, participation, off-exchange activity, Daily Top rankings, MACD, Bollinger Bands, trend and sorting. Also manages the customer's saved Master Scanner scans: list, run, save, change, reset or delete. Saved scans persist normalized rules, not the current result tickers. After a Pattern search/refinement, save this scan should reuse that active search's Pattern + Master Scanner rules when safely representable. Prefer this tool for requests such as 'run a master scan', 'find pre-breakouts with rising OBV and an EMA 8/20 cross in the last 3 days', 'run my saved scan', or 'save this scan'. Results come from the same reusable Master Scanner core as the website; do not recreate or approximate scanner logic in ChatGPT. Treat scanner results as technical screening information and do not convert them into personalised buy/sell instructions.

master_scanner

Primary tool whenever the user's intent is pressure building or PBI: highest PBI, strongest pressure, stocks building pressure, top pressure stocks, strongest build-ups, or PBI leaders. Returns compact leader records for the highest current EdgeBreak Pressure Building Index scores across the full daily scanned universe. Present returned multi-stock results in the branded EdgeBreak results card rather than a generic ChatGPT markdown table. PBI rank is ranking within the PBI universe and is NOT Daily Top 20 or Daily Top 6 rank; when universe_count is available, include that returned count in the customer-facing rank wording rather than hard-coding a universe size or using an ambiguous 'Rank #1'. If the user also asks to see charts, call show_stock_chart for the requested tickers. These are EdgeBreak research records, not investment recommendations.

get_pbi_leaders

Use for the wider EdgeBreak paid research experience beyond scanner intelligence. Returns one selected research section for a NASDAQ ticker: company overview, financials, institutional research, recent company news, SEC filings, or current market attention. Use get_stock_intelligence for scanner/technical/PBI questions. Use recent_news for news requests and market_attention for attention/discussion requests even though EdgeBreak may research and cache those together internally. Preserve reporting periods and filing dates, do not present lagged institutional disclosures as real-time activity, and do not turn factual research into investment advice.

get_company_research

Primary customer-facing EdgeBreak V1 journey for browsing current published Pre-Breakouts, Breakouts and PBI stocks, narrowing an existing result set with supported EdgeBreak master-data filters, rendering branded comparisons for 2–5 named or remaining stocks, opening a Stock Hub, navigating back without losing filters, managing the customer's EdgeBreak watchlist, and answering watchlist-level support/breakdown questions from completed EdgeBreak chart history. Use this tool when the user is exploring EdgeBreak interactively or continuing a scanner workflow in natural language. For comparison intent, prefer this tool over a generic markdown table so the EdgeBreak comparison UI renders. It preserves scanner/date/filter/result/stock state and never reruns or changes scanner formulas. If a requested EdgeBreak V1 action is unsupported or ambiguous, preserve the customer's current state and use closest_supported or continue_journey to surface the nearest valid path rather than dropping context. The customer can always continue normally in ChatGPT. For a standalone visual chart request use show_stock_chart immediately; for detailed company research use get_company_research.

edge_journey

Use when the user asks to filter or sort the latest published EdgeBreak breakout scan by explicit conditions such as price, published score, volume ratio, breakout strength, touches, higher lows, rank, grade, price group or setup type. Typical requests include 'stocks under $10 with strong volume', 'setups with at least three touches', or 'filter the scanner'. Present returned multi-stock results in the branded EdgeBreak results card rather than a generic ChatGPT markdown table. If the user says 'strong volume' without giving a threshold, apply the explicit filters they did give and sort by published volume_ratio descending rather than inventing an arbitrary cutoff. Do not use for a plain latest scan, plain PBI leaders, a broad single-stock assessment, or the dedicated Pre-Breakout list. For 'near resistance', 'about to break out', or 'hasn't broken out yet', prefer get_pre_breakout_scan unless the request is specifically to filter the breakout scan. Operates only on already-published EdgeBreak fields and never exposes proprietary methodology.

search_signals

Use for a ticker's past EdgeBreak breakout appearances: whether it appeared before, when it showed up, how many times it was picked, or its previous published breakout signals. Returns verified historical EdgeBreak breakout-session records from retained full daily snapshots plus validated exact historical scanner versions. This history may still be incomplete before the published coverage_start date. A zero-match result must NOT be presented as proof that the ticker never appeared outside the verified coverage window. Use the returned session count and coverage dates in customer-facing wording. This is EdgeBreak signal history, not general market-price history; use show_stock_chart for a visual price chart or get_stock_chart_data for raw OHLCV history. If the user asks for past appearances and what the stock looks like now, combine with get_stock_intelligence.

get_signal_history

Primary tool for stocks approaching a breakout before it happens. Use for natural requests such as 'about to break out', 'close to breaking out', 'getting ready to break', 'near resistance', 'pre-breakout stocks', 'stocks setting up', 'early setups', 'building a base', 'potential breakouts', or 'what hasn't broken out yet'. Returns the latest published EdgeBreak Pre-Breakout Scanner in published order. Present returned multi-stock results in the branded EdgeBreak results card rather than a generic ChatGPT markdown table. For superlative requests such as 'closest to resistance', request enough published results to compare the available distance_to_resistance values before answering; do not invent a new scanner score. Treat published position as list order, not proof of overall quality or liquidity: prefer wording such as 'leading published Pre-Breakout results' rather than 'best' or 'strongest' unless published fields explicitly support that claim. Use search_signals instead when the user is primarily asking for custom filters on the latest breakout scan. If the user asks which pre-breakout names have the strongest pressure, combine published Pre-Breakout results with PBI/intelligence data only as needed. Never expose EdgeBreak methodology.

get_pre_breakout_scan