Skip to main content
Glama

Search SEC Filings

search_sec_filings

Search SEC EDGAR filings by CIK number, form type, company name, or date range to access filing metadata and document URLs for financial research and compliance.

Instructions

Search SEC EDGAR filings by CIK number, form type (10-K, 10-Q, 8-K, etc.), company name, and date range. Returns filing metadata including accession number, filing date, and document URLs. Source: SEC EDGAR, updated every 15 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoCentral Index Key — SEC's unique company identifier (e.g. 0001652044 for Alphabet)
form_typeNoSEC form type (e.g. 10-K, 10-Q, 8-K, S-1, DEF 14A). Case-insensitive.
company_nameNoCompany name to search for (partial match)
date_fromNoStart date for filing date range (YYYY-MM-DD)
date_toNoEnd date for filing date range (YYYY-MM-DD)
limitNoMaximum number of results (default 25, max 100)

Implementation Reference

  • src/tools/sec.ts:41-82 (registration)
    Registration of the 'search_sec_filings' tool including title, description, and input schema.
    server.registerTool(
      "search_sec_filings",
      {
        title: "Search SEC Filings",
        description:
          "Search SEC EDGAR filings by CIK number, form type (10-K, 10-Q, 8-K, etc.), " +
          "company name, and date range. Returns filing metadata including accession number, " +
          "filing date, and document URLs. Source: SEC EDGAR, updated every 15 minutes.",
        inputSchema: {
          cik: z
            .string()
            .optional()
            .describe(
              "Central Index Key — SEC's unique company identifier (e.g. 0001652044 for Alphabet)",
            ),
          form_type: z
            .string()
            .optional()
            .describe(
              "SEC form type (e.g. 10-K, 10-Q, 8-K, S-1, DEF 14A). Case-insensitive.",
            ),
          company_name: z
            .string()
            .optional()
            .describe("Company name to search for (partial match)"),
          date_from: z
            .string()
            .optional()
            .describe("Start date for filing date range (YYYY-MM-DD)"),
          date_to: z
            .string()
            .optional()
            .describe("End date for filing date range (YYYY-MM-DD)"),
          limit: z
            .number()
            .int()
            .min(1)
            .max(100)
            .optional()
            .describe("Maximum number of results (default 25, max 100)"),
        },
      },
  • Handler function for 'search_sec_filings' which calls the SEC filings API.
      async ({ cik, form_type, company_name, date_from, date_to, limit }) => {
        const res = await apiGet<SecFilingsResponse>("/api/v1/sec/filings", {
          cik,
          form_type,
          company_name,
          date_from,
          date_to,
          limit: limit ?? 25,
        });
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const summary = `Found ${count} SEC filing(s).`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the data source (SEC EDGAR) and update frequency (every 15 minutes), which is useful context. However, it does not mention rate limits, authentication requirements, pagination behavior (beyond the 'limit' parameter), or error handling, leaving gaps for a search tool.

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 core functionality, followed by return details and source information. Every sentence adds value: the first specifies search criteria, the second describes returns, and the third provides source context. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (search tool with 6 parameters) and lack of annotations or output schema, the description is reasonably complete. It covers purpose, parameters, returns, and data source. However, it could improve by addressing behavioral aspects like rate limits or result ordering, which are not in the schema.

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%, so the schema fully documents all 6 parameters. The description lists the searchable fields (CIK, form type, company name, date range) but adds no additional meaning beyond what the schema provides, such as how multiple parameters interact or search logic details. Baseline 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 clearly states the specific action ('Search SEC EDGAR filings') and resources involved (filings by CIK, form type, company name, date range). It distinguishes itself from sibling tools like 'get_sec_filing' (likely for retrieving specific filings) and 'search_sec_companies' (likely for company metadata rather than filings).

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

Usage Guidelines3/5

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

The description implies usage for searching SEC filings with various filters, but does not explicitly state when to use this tool versus alternatives like 'get_sec_filing' (for retrieving a specific filing) or 'search_sec_companies' (for company information). No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrierone/verilexdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server