Annalist Financial Statements

Get corporate events

get_events

Read-onlyIdempotent

Corporate events of a company found by fixed rules in its filings: acquisitions, disposals, spin-offs, discontinued operations, reorganisations, stock splits, restatements, name changes and changes of fiscal year, each with its date, fiscal period, a sentence, the counterparty and amount where the filing names them, and its source document ids. Events are recorded for companies that file with the SEC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "get_events"
  }
}

Input Schema

Name	Required	Description
`at`	No	an ISO date: the snapshot that was the latest on that date, in place of the latest snapshot
`to`	No	last date, in the same forms
`from`	No	first date: a year (2024) or an ISO date
`types`	No	keep these event types
`company`	Yes	company id from search_companies, for example apple or mizuho

Output Schema

Name	Required	Description	Default
`name`	No
`note`	No
`as_of`	No
`total`	Yes
`types`	No
`events`	Yes
`company`	Yes
`matched`	Yes
`citation`	Yes
`snapshot`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds valuable context beyond that: events are detected by fixed rules in filings, coverage is limited to SEC filers, and each event includes source document ids and extracted details.

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?

The description is front-loaded and dense, but it repeats the full event-type list that is already present in the schema enum. That redundancy is useful for purpose clarity but slightly reduces conciseness.

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?

With a complete input schema, an output schema, and annotations covering safety, the description supplies the remaining context needed: data provenance, SEC coverage, and an overview of returned fields.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already fully documents company, from, to, at, and types. The description does not add parameter-level meaning; the baseline 3 applies.

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?

The description names a specific resource—corporate events of a company—and enumerates the event types and return fields precisely. It clearly distinguishes the tool from financial-statement, ratio, or search siblings.

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

Usage Guidelines3/5

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

Usage is implied: call this to retrieve corporate events for a company. The only guidance is the scope note that events are recorded for SEC filers; there is no explicit when-to-use, when-not-to-use, or alternative tool named.

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

All Annalist Financial Statements 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?