Search and retrieve SEC filings by company symbol using the FMP SEC Filings By Symbol API. Gain direct access to regulatory filings such as 8-K, 10-K, and 10-Q reports for publicly traded companies.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | End date (YYYY-MM-DD) | |
| from | Yes | Start date (YYYY-MM-DD) | |
| page | No | Page number for pagination | |
| limit | No | Limit the number of results | |
| symbol | Yes | Stock symbol |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves filings but does not disclose important behaviors like pagination (page/limit), required date range parameters, response format, potential filtering by form type, or how errors are handled. This is insufficient for a tool with no annotation safety hints.
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 two sentences, front-loaded with the main verb and resource, and contains no redundant filler. It efficiently conveys the purpose and examples of filings without unnecessary detail.
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?
The tool has 5 parameters, no output schema, and no annotations. The description clearly identifies what the tool does, but lacks return value expectations, usage alternatives, and behavioral details like pagination. It is minimally viable for selection but not fully complete for confident invocation.
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 the baseline is 3. The description adds context about filing types but does not elaborate on parameter semantics beyond the schema. It does not explain symbol format, date range meaning, or pagination behavior, but the schema already documents each parameter adequately.
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 the action ('Search and retrieve'), the resource ('SEC filings'), and the specific scope ('by company symbol'). It also differentiates from siblings like getFilingsByCIK and getFilingsByFormType by emphasizing the symbol-based lookup, and mentions concrete filing types (8-K, 10-K, 10-Q).
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 provides no explicit guidance on when to use this tool versus alternatives such as getFilingsByCIK, getFilingsByFormType, or getLatest8KFilings. It only implies usage by mentioning 'by company symbol', but does not state exclusions or preferability conditions.
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.