Get Form 8-K material event filings — M&A announcements, CEO changes, earnings releases, and other events requiring immediate SEC disclosure.
| Name | Required | Description | Default |
|---|---|---|---|
| cik | No | SEC CIK number | |
| limit | No | Number of events | |
| ticker | No | Stock ticker symbol |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description only mentions content type (8-K filings). No disclosure of API limits, pagination, response format, or behavior when parameters are omitted. No annotations to compensate.
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?
Single sentence, front-loaded with purpose, including examples. No wasted words.
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?
No output schema; does not explain return data or how to combine optional parameters (cik vs ticker). For a tool with 3 optional params, more context is needed.
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 provides 100% coverage of parameters (cik, limit, ticker) with basic descriptions. Description adds no further meaning beyond examples.
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?
Description clearly states the tool retrieves Form 8-K material event filings with specific examples (M&A, CEO changes, etc.). It distinguishes itself from siblings implicitly, but lacks explicit differentiation.
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?
No guidance on when to use this tool vs alternatives (e.g., get_earnings_data). Does not specify prerequisites or exclusions.
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.