get_company_snapshot
Read-only
Fetch a structured, POINT-IN-TIME company snapshot — no report generation needed.
Returns thesis/bull/bear, financial overview (Piotroski, valuation signal),
price performance + technical indicators, price targets, institutional
ownership, and analyst grades for `symbol`. Synchronous and cheap — prefer
this for a quick CURRENT read instead of generating a full PDF report.
*** POINT-IN-TIME ONLY — THIS IS NOT A TIME SERIES. *** It captures where the
company stands right now, not how it got there. Do NOT use it to answer
temporal / trend / "over time" questions (e.g. "how has X evolved over the
past year", "quarter-over-quarter trend", "activity over the last 12 months",
"since ..."). Each block is an independently-sourced current cut with its own
as-of date (e.g. the institutional-ownership block is the latest 13F holder
snapshot), so the blocks are NOT a comparable historical series — reading a
trend off them, or treating two blocks' as-of dates as the same instant,
produces spurious results. For anything time-series, historical, or
"how did this change", use `explore_data_catalogue` instead.
Scope caveat: the snapshot is a FIXED set of current blocks, not the full
catalogue. Absence of a data domain HERE does NOT mean Flexreport lacks it —
do not infer coverage gaps from this tool. Route "which symbols / values are
available" enumerations to `list_options` (instant), and "do you have data
on <topic>" questions that need actual data to `explore_data_catalogue`.
*** RUN IT WITH `get_company_event_web(symbol)` — THE STANDARD PAIR. *** This
tool gives the WHAT (where the company stands); the event web gives the WHY
(the events that got it there, in order, and how they connect). The snapshot
states that the thesis shifted, the valuation signal changed, or ownership
moved; it does NOT say what caused any of it — every block here is a settled
output with the episode behind it stripped out. So whenever the user asks
about a company generally, or follows a snapshot with "why?" / "what changed?"
/ "what drove that?", call BOTH and read them together: quote the snapshot for
the current position, and the event web for the sequence that explains it.
Presenting a snapshot alone as the whole picture is the failure mode — it
reads as a verdict with no evidence.
Two honest limits when pairing them. (1) The event web defaults to a 7-day
window; a driver older than that needs `window_days` widened (up to 90) before
you can say the snapshot is unexplained. (2) The blocks here carry their own
as-of dates — a 13F ownership block can be a quarter old, so the event that
explains it may sit well outside any window. Absence of a matching event is
NOT proof the snapshot moved for no reason.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Covered ticker, e.g. "AAPL". |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| recent_news | No | ||
| price_targets | No | Decommissioned pending a model revamp: values are null and active_coverage is false. | |
| price_overview | No | ||
| company_summary | No | Thesis, bull and bear case. | |
| financial_overview | No | ||
| stock_grades_overview | No | ||
| institutional_ownership | No |