Skip to main content
Glama

Events since a date

what_changed
Read-only

Returns what was recorded since a date (default 7 days, up to 90): SEC filings accepted, figures a company restated, technical signals and ownership declarations. By default (highlights) ranked by materiality, repeats grouped; detail: 'events' is the raw list, newest first. With symbol, one company: a 13F row then says what that manager did of it (quarterMove). Price moves are not events here (see get_company). When complete is false, pass next.until as until for the page before; howToRead in the answer explains each row. Use it for a daily or weekly brief, or when the user asks what changed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "what_changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHighlights: rows to return (default 40, max 100). Events: events to return (default 50, max 200).
sinceNoISO date or timestamp to look back from (default: 7 days ago). At most 90 days back: an older date is moved to that limit and `window.windowClamped` says so.
untilNoISO date or timestamp to read up to, included (default: now). Pass the previous answer's `next.until` to read the next page.
detailNo'highlights' (default): ranked, grouped summary of the window. 'events': the raw list, newest first.
symbolNoRestrict to one ticker. Omit for the whole universe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"ISO date or timestamp to look back from (default: 7 days ago, maximum 90 days)."New value: +"ISO date or timestamp to look back from (default: 7 days ago). At most 90 days back: an older date is moved to that limit and `window.windowClamped` says so."
  2. Changed1 schema field changed
    • addedInput schema / properties / until
      Added value: +{
      +  "description": "ISO date or timestamp to read up to, included (default: now). Pass the previous answer's `next.until` to read the next page.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, so the description's added value is what it discloses beyond them: the 7-day default and 90-day clamp with `window.windowClamped` flagging the adjustment, the pagination contract ('When `complete` is false, pass `next.until` as `until` for the page before'), and response-shaping details (`howToRead` per row, `quarterMove` on 13F rows when `symbol` is set). These are non-obvious behaviors an agent could not infer from annotations.

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-loads what it returns, then modes, then the sibling exclusion, then pagination — a sensible order with no filler sentences. It is dense to the point of being run-on (parenthetical backticks stack up mid-sentence), which slightly taxes first-pass parsing, but every clause carries information.

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

Completeness4/5

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

With no output schema, the description carries the return-value burden and mostly meets it: mode differences, pagination cursor, `howToRead`, `windowClamped`, `quarterMove`. What is left thin is the overall envelope (ordering across modes, what `complete` means at the top level), which is referenced but not defined.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real semantics the schema does not: `detail: 'events'` being newest-first raw versus ranked/grouped highlights, and the `symbol` parameter changing row shape by appending `quarterMove`. It also ties `until` to a returned `next.until`, clarifying pagination intent beyond the field's own wording.

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 ('returns what was recorded since a date') and immediately enumerates the event types covered: SEC filings, restatements, technical signals, ownership declarations. It also draws a bright line against the nearest confusion case ('Price moves are not events here (see get_company)'), so the agent can separate it from price/market siblings 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 Guidelines4/5

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

Gives an explicit exclusion with a named alternative ('Price moves are not events here (see get_company)') and a positive use case ('a daily or weekly brief, or when the user asks what changed'). It stops short of routing to the raw-resource siblings (get_filings, get_signals, get_holders), which return the underlying items this tool aggregates, so the when-to-use-vs-which-sibling picture is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.