Stocklake — AI Stock Intelligence

Get Stock Activity

get_stock_activity

Read-onlyIdempotent

Everything that happened to one stock over the last 90 days, in one timeline, newest first: news, SEC 8-K filings, insider clusters and large single trades, earnings dates and reported results, analyst target and rating changes, and screener setups. Answers "what has been going on with this stock?" in one call instead of five.

Each item has a type (news | filing | insider | earnings | analyst | setup), an ISO timestamp, a plain headline and a type-specific extra object. With no types the timeline is the "All" view: very weak news is left out and upcoming earnings within 30 days are returned separately under upcoming; with types you get just those kinds, news included in full (for Pro; see below for Free). counts is how many items of each kind exist in the window, whatever the page or filter; with no types its sum can exceed total, because the all-types list leaves out very weak news, shows a reported quarter once and lists upcoming dates separately.

What each type is:

news: an article about the company (third-party reporting; the headline is the article's own).
filing: an SEC 8-K, with its item labels. Earnings coverage that repeats a results filing is folded into it (extra.related_news). Filings are recorded for US-listed companies in USD with a market cap of about $1 billion or more.
insider: a cluster of 3 or more insiders buying or selling within 30 days, with the amount in the headline.
earnings: a reporting date (extra.date, extra.upcoming, extra.estimate), or a reported quarter. Where its EPS can be matched to the analysts' estimate, the headline says whether EPS beat, missed or was in line with estimates; Pro's content adds the figures. A stock with no estimate data keeps its row as it was.
analyst: the consensus target or rating moved by 5% or more; consecutive steps in one direction are one item.
setup: a screener setup flagged on the stock (Pro).

Every account gets the facts: all types except setups over the 90 days, with the plain headline in full and the same page size. Three allowances match the other Free tools: Free returns the 5 newest articles of the last 30 days (as get_stock_news does; news_note says so), the 5 most recent SEC 8-K filings (as get_stock_filings does; filings_note says so), an analyst item names the direction only, and so does an EPS beat or miss on a reported quarter (never the estimate or a percentage). Pro adds related news and filings, and these fields: tone (Positive/Negative/Neutral, describing the news for the company, not a price call), number with its number_label (a 0-100 score for news and setups, relevance for filings), a short summary, the model's own filing headline, fuller extra fields (analyst target and rating levels, insider total value and trades), and the setup items themselves (everyone else is told only that the stock has some, under locked_types; the number is not sent).

Not the same as get_signals, which is the market-wide queue of freshly screened ideas across all stocks (Pro, last 24 hours, ranked by signal_score). A setup here is one such idea for this stock, one item among six kinds in its history. For articles alone use get_stock_news; for filings alone, get_stock_filings.

If a source could not be read just now, status is "partial" and unavailable lists the kinds left out (of those you asked for): an empty list for them does not mean nothing happened. Call again shortly. For informational purposes only. Not financial advice.

Input Schema

Name	Required	Description
`days`	No	Look-back window in days (default 90, max 90).
`page`	No	Page number, starting at 1. `pages` in the response says how many there are.
`limit`	No	Items per page (default 25, max 50). The whole call counts as one call toward your daily limit.
`types`	No	Which kinds of items to return: any of "news", "filing", "insider", "earnings", "analyst", "setup" (default: all). Unknown names are an error that lists the valid ones.
`symbol`	Yes	Stock ticker symbol. Also accepts a company name as a fallback when it uniquely resolves to one symbol.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only safety profile, yet the description adds far more: `status: "partial"` with an `unavailable` list and the warning that an empty list there does not mean nothing happened, call-again guidance, the Free/Pro split with named note fields (`news_note`, `filings_note`, `locked_types`), and coverage limits (8-Ks only for US-listed USD companies above ~$1B cap).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with a one-line summary, then cleanly sectioned into per-type definitions, tier differences, alternatives and failure modes — all of which carry load given six item types. It is dense rather than padded, but the Free-allowances sentence ('Three allowances match the other Free tools: ... and so does an EPS beat or miss') is garbled and enumerates four things under a count of three, and 'see below for Free' is a forward reference that could be inline.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-source, tiered, paginated aggregation tool this covers everything an agent needs: what each `type` contains via its `extra` fields, the upcoming-earnings edge case, pagination/counts semantics, degraded-source handling, and Free-vs-Pro field gating. The output schema exists so return shapes needn't be described, yet the description still tells the agent which fields appear conditionally.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description meaningfully deepens `types`: omitting it yields the 'All' view that drops very weak news and separates upcoming earnings under `upcoming`, while specifying it returns those kinds with news in full — plus why `counts` can sum above `total`. That is behavioral semantics the schema's 'Which kinds of items to return' does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with explicit scope: 'Everything that happened to one stock over the last 90 days, in one timeline, newest first,' and enumerates the six item kinds. It also names the sibling tools it is not (get_signals, get_stock_news, get_stock_filings), so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use framing ('Answers "what has been going on with this stock?" in one call instead of five') plus when-not: 'For articles alone use get_stock_news; for filings alone, get_stock_filings,' and a full paragraph distinguishing the setup item from get_signals' market-wide queue.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Stocklake — AI Stock Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?