Retrieve SEC Form 8-K material event filings — M&A, executive changes, bankruptcy, earnings, going concerns. Replaces an 8-K Push subscription. Real-time material event monitoring for any public company.
Args: ticker: Optional ticker filter event_type: Optional 8-K item filter (e.g. "1.01", "2.01", "5.02") days_back: Lookback window in days (default 14)
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | No | ||
| days_back | No | ||
| event_type | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, confirming a safe read operation with possibly open-world results. The description adds 'Real-time material event monitoring' but does not elaborate on data freshness, update frequency, consistency guarantees, or any side effects. No contradictions found.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise: one sentence for purpose, one for value proposition, and a structured Args list. No excessive text; front-loaded with the core verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a retrieval tool with 3 optional parameters and no output schema, the description covers purpose, parameters, and real-time aspect. Output format is not described, which is a gap but acceptable given lack of output schema. Overall adequately complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description carries the full burden. It explains each parameter: ticker (optional filter), event_type (with example values like '1.01', '2.01', '5.02'), and days_back (lookback window, default 14). This adds meaningful context beyond the schema's type/defaults.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Retrieve SEC Form 8-K material event filings' with specific event types (M&A, executive changes, bankruptcy, earnings, going concerns). It clearly distinguishes from sibling tools like get_form_13f_holdings and get_form_4_insider_trades, making its unique purpose immediately obvious.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for 8-K monitoring ('Replaces an 8-K Push subscription', 'Real-time material event monitoring') but lacks explicit guidance on when to use this tool versus alternative form tools (e.g., get_form_13f_holdings). No when-not-to-use or prerequisite conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct regulatory filing or financial data type with clear, non-overlapping descriptions. Even similar concepts like 13F holdings vs. delta are well-differentiated.
Most tools follow a consistent 'get_<noun>' pattern, with a single exception 'detect_insider_cluster'. Overall naming is predictable and readable.
17 tools is slightly above the ideal 3-15 range but justified by the broad domain of regulatory filings and financial data. Each tool serves a clear purpose.
The server covers a comprehensive set of regulatory filings (13F, Form 4, 8K, etc.) and additional financial data (analyst targets, options, short interest). Minor gaps like Form 144 are acceptable given the scope.