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. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It describes what the tool retrieves but does not mention rate limits, pagination, or response format, leaving gaps in transparency.
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 a single, efficient sentence with relevant examples, earning its place without fluff.
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 exists, and the description lacks details on behavior or parameter usage. While sufficient for a simple listing tool, it could be more 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 100%, so baseline is 3. The description adds context about the types of events but does not enhance understanding of parameters beyond what the schema provides.
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 clearly states 'Get Form 8-K material event filings', specifying the verb and resource, and provides concrete examples like M&A announcements and CEO changes, distinguishing it from siblings such as get_earnings_data and get_fda_data.
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 SEC material events but offers no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it.
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.
Most tools target distinct SEC-related data (earnings, insider trades, material events, filings), but get_material_events and get_recent_filings both handle 8-K filings, creating minor overlap. The FDA data tool is wholly unrelated, increasing potential confusion about the server's scope.
All tool names follow a consistent 'get_{category}_data' or 'get_{entity}' pattern (e.g., get_earnings_data, get_insider_trades). The verb_noun structure is uniform and predictable, aiding agent selection.
With 5 tools, the count is reasonable, but the inclusion of get_fda_data (FDA, not SEC) makes the set feel scattershot rather than focused. The server title 'SEC Filings & Earnings' suggests a narrower scope, so the tool count includes an outlier.
For SEC filings, the server covers key types: XBRL earnings, insider trades (Form 4), material events (8-K), and a general filings search. Missing structured 10-K/10-Q data and filing text retrieval are minor gaps. The FDA tool is an unrelated addition, not a gap.