Zovo SEC Filings

Latest SEC filings

find_latest_filings

Read-onlyIdempotent

Use this when the user wants the latest SEC filings or EDGAR search results for a US public company, for example the latest 10-Q, 8-K filings, or a 10-K. Reads live SEC EDGAR submissions data and returns each filing's form, filing date, report date, description and a link to the document on sec.gov. Returns the 1,000 most recent submissions held by EDGAR's API; older filings are not included. Do not use for share prices, insider trading analysis, or investment advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "find_latest_filings"
  }
}

Input Schema

Name	Required	Description
`forms`	No	Filing types to include: a subset of 10-K, 10-Q, 8-K, S-1, DEF 14A, 20-F. Default 10-K, 10-Q, 8-K. Example: ["10-K","8-K"].
`limit`	No	Maximum number of filings to return, a whole number 1 to 40 (default 12). Example: 10.
`company`	Yes	Company ticker or name, e.g. AAPL or Apple. US-listed companies in the SEC EDGAR index.

Output Schema

Name	Required	Description	Default
`cik`	Yes
`count`	Yes
`forms`	Yes
`notes`	Yes
`query`	Yes
`source`	Yes
`status`	Yes
`ticker`	Yes
`company`	Yes
`filings`	Yes
`candidates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, which already establish that this is a read-only, idempotent, non-destructive operation, the description adds important behavior: it reads live SEC EDGAR submissions data, returns specific filing fields, and is capped at the 1,000 most recent submissions. That cap and the exclusion of older filings are exactly the kind of behavioral detail an agent needs.

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?

The description is front-loaded with the primary use case, followed by return behavior and exclusions. Every sentence adds useful information, and there is no redundant or wasted 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?

The tool has rich annotations, full schema description coverage, and an output schema. The description still supplies the key operational caveat about EDGAR's 1,000-submission limit and the live data source, making the definition complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents company, forms, and limit with examples and constraints. The description reinforces the company scope and filing types but does not add syntax or format details beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: finding the latest SEC filings or EDGAR search results for a US public company, with concrete examples such as 10-Q, 8-K, and 10-K. It also distinguishes the tool from unrelated use cases, so an agent can identify its role without inspecting the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool, gives filing-type examples, and names exclusions: share prices, insider trading analysis, and investment advice. This leaves little ambiguity about when this tool is appropriate versus when it is not.

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

All Zovo SEC Filings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?