Skip to main content
Glama

Edgrapi — SEC EDGAR Financials

by com.edgrapi.api

Get 8-K material events

get_events
Read-onlyIdempotent

8-K material events for a ticker as typed items (2.02 earnings, 5.02 executive change, 1.05 cybersecurity incident, 2.01 acquisition, etc.), each with a notable flag for the market-moving ones and a link to the filing. Pass item to filter to one event type (e.g. '4.02' for every restatement a company filed). Pass ticker='restatements' or 'auditor-changes' for the market-wide red-flag feed of recent item 4.02 / 4.01 8-Ks across all filers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoFor the market-wide feeds: lookback window in days (default 45).
itemNoFilter to a specific 8-K item code, or comma-separated codes, e.g. '4.02' (restatement) or '5.02,2.02'.
limitNoNumber of events, 1-100 (default 20; 50 for feeds).
tickerYesUS stock ticker (e.g. 'AAPL'), or 'restatements' / 'auditor-changes' for the market-wide item feed.
notableNoOnly market-moving events (default false).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent, so no safety disclosure is needed; the description adds behavior beyond annotations: returned events are typed items, have a notable flag for market-moving events, include a filing link, and support a market-wide red-flag feed for items 4.02/4.01. It does not contradict annotations.

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?

Three sentences, all substantive: purpose and output elements are front-loaded, then filtering and special feeds. There is no filler or repetition of schema text.

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 moderate-complexity read-only tool with fully described parameters and safety annotations, the description covers the main output elements and the two special modes. An agent can select and call it correctly without additional information.

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 covers all five parameters with descriptions (100% coverage), so baseline is 3. The description adds meaning beyond the schema by mapping item codes to real-world event types (2.02 earnings, 4.02 restatement), explaining the notable-flag concept, and clarifying the special ticker feed behavior.

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 ('Get') and resource ('8-K material events') with defining details: typed items, notable flag, filing link, and special market-wide feeds. This clearly distinguishes it from sibling tools like get_filings or search_filings by scoping to 8-K event type items.

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 explicit usage context for filtering by item code and for the special ticker values 'restatements'/'auditor-changes', which is more than implied usage. It does not explicitly name alternatives or when-not-to-use, but the main use case and special modes are clear.

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

All Edgrapi — SEC EDGAR Financials toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct SEC EDGAR resource and action: company info, filings, fundamentals, ratios, insider trades, activist stakes, fund holdings, events, and narrative sections. There is no overlap in purpose, and descriptions clarify any potential ambiguity (e.g., get_activist vs get_holdings).

Naming Consistency5/5

All tools follow a consistent 'get_' prefix followed by a singular or plural noun (e.g., get_company, get_filings, get_ratios). The pattern is uniform and predictable, making it easy to infer behavior from the name.

Tool Count5/5

Nine tools is well-scoped for a financial data server covering company profiles, regulatory filings, and derived metrics. Each tool has a clear, non-redundant role, neither feeling sparse nor bloated.

Completeness4/5

The surface covers the core EDGAR resources: company metadata, filings, financial statements, ratios, insider activity, activist filings, fund holdings, material events, and narrative sections. Minor gaps exist (e.g., direct search for specific filing types or proxy statements), but agents can accomplish most research workflows without dead ends.

Resources