Skip to main content
Glama

filingpulse

by io.filingpulse
OverviewDiscussionsAdmin

8-K corporate events

get_corporate_events
Read-only

List SEC 8-K corporate events classified by official item code, newest first — e.g. 2.02 results of operations, 5.02 executive/director changes, 1.01 material agreements, 7.01 Reg FD. Filter by item code, issuer ticker or CIK, or since-date. Returns a {data, total, limit, offset} envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoSEC CIK number, digits only (leading zeros optional).
itemNoOfficial 8-K item code, e.g. 2.02 or 5.02.
limitNoRows to return (max 25 on this endpoint).
sinceNoOnly filings filed on/after this date (YYYY-MM-DD).
untilNoOnly filings filed on/before this date (YYYY-MM-DD) — with since, a fixed reproducible window.
offsetNoRows to skip — page through 'total' with limit+offset.
tickerNoIssuer ticker symbol, e.g. KMI. 8-K headers carry no ticker, so it is resolved to a CIK via this dataset's Form 4 filings — an issuer with no Form 4 yet needs 'cik' instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • addedInput schema / properties / ticker
      Added value: +{
+  "description": "Issuer ticker symbol, e.g. KMI. 8-K headers carry no ticker, so it is resolved to a CIK via this dataset's Form 4 filings — an issuer with no Form 4 yet needs 'cik' instead.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's contribution is the disclosure that results are sorted newest-first and returned in a {data, total, limit, offset} envelope. The paginated envelope shape is genuinely useful context an agent cannot infer from annotations, though permission/rate-limit behavior remains unstated.

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

Conciseness5/5

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

Two tightly packed sentences: the first defines the resource and its ordering, the second covers filtering and the return envelope. Nothing is redundant and the highest-value information leads.

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?

No output schema exists, so the description fills that gap by naming the response envelope, and all seven parameters are documented in the schema. For a read-only filtered listing endpoint, an agent has everything needed to call it correctly.

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 every parameter is already documented in the schema, including the ticker-to-CIK resolution caveat. The description restates the filterable fields but adds no syntax, defaults, or constraints beyond what the schema provides, making 3 the correct baseline.

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+resource ('List SEC 8-K corporate events') with classification scope ('by official item code') and ordering ('newest first'), which cleanly separates it from siblings like get_insider_filing and get_ipo_registrations.

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?

Enumerates the available filter axes (item code, issuer ticker, CIK, since-date) and gives concrete item-code examples, so the agent knows how to scope a query. It never names a sibling as an alternative or states when a different tool would be preferable, so it stops short of explicit when-not guidance.

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

All filingpulse toolsInspect
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