WatchMyCompetitor

Answers a market-intelligence question using the WMC knowledge base. Returns a clean answer, source alerts with WMC links, and reusable sessionId for follow-up questions.

threads_ask

Retrieves full underlying alert records or payloads for supplied identifiers. Use this tool when the user explicitly requests complete alert details rather than a summary. When retrieving full alert payloads referenced by threads_ask: 1. Reuse sessionId from the threads_ask response. 2. Pass its alertIds as alerts. 3. Pass its intelType as contextHints.intel_type so the correct source system is used. Microsoft 365 Copilot may omit alert identifiers and sessionId between tool calls. When that happens, the server automatically retrieves alerts from the authenticated caller's most recent completed threads_ask session. The correlation is tenant- and caller-scoped and expires after 15 minutes. threads_ask already returns human-readable evidence and links. Call getAlerts only when the user explicitly asks for the full underlying alert records or payloads.

getAlerts

Retrieves the full alert records referenced by a WMC conversation thread. Use this tool when the user explicitly asks for the underlying alerts from the current or previous WMC answer. This tool: 1. Looks up the thread ID from the session context 2. Fetches thread history from Threads AI API 3. Extracts alert IDs and intel_type based on the extraction mode 4. Retrieves full alert payloads using the alert broker infrastructure Extraction Modes: - 'Last' (default): Extracts all alerts from the most recent message only - 'All': Extracts all unique alerts from the entire thread history (deduplicates across messages) Microsoft 365 Copilot may not forward sessionId between tool calls. When the preceding threads_ask result contains alertIds, pass those numeric identifiers in alertIds (or alerts) and pass intelType directly (or in contextHints.intel_type). Never parse an alertId from a WMC URL. If only a publicKey or WMC URL is available, pass it through alertReferences. This explicit-alert path is preferred and does not depend on session correlation. When alerts and sessionId are not supplied, the server automatically uses the authenticated caller's most recent completed threads_ask session. The correlation is tenant- and caller-scoped and expires after 15 minutes.

threads_getAlerts

Use this when the user asks what a tracked company or competitor has done, changed, launched, announced or published during a time period. Uses the authenticated WatchMyCompetitor Knowledge Base and returns an evidence-backed summary. Do not use for general public-web company facts or untracked companies.

summarize_company_activity