Skip to main content
Glama

Sec Xbrl Search Filings

sec_xbrl_search_filings
Read-onlyIdempotent

Search recent SEC filings for a company by CIK. Optionally filter by filing type (10-K, 10-Q, 8-K, etc.). Returns filing dates, types, and accession numbers.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cik": "320193"
    },
    "name": "sec_xbrl_search_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesSEC Central Index Key (e.g., "320193" for Apple)
typeNoFiling type filter (e.g., "10-K", "10-Q", "8-K", "DEF 14A")

Output Schema

NameRequiredDescriptionDefault
cikYesSEC Central Index Key
sicYesStandard Industrial Classification code
nameYesLegal name of the company
filingsYesUp to 25 recent filings
tickersYesStock ticker symbols
exchangesYesStock exchange listings
filing_countYesTotal number of filings matching criteria
sic_descriptionYesIndustry description from SIC
state_of_incorporationYesState where company is incorporated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. Beyond that the description adds only the scope hint 'recent' and the returned field list, but never defines the recency window, result count, or any SEC rate-limit behavior — meaningful omissions for a live external API.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and followed by the optional filter and the return shape. No filler, though the return-field sentence partly duplicates what the output schema already conveys.

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?

For a two-parameter, read-only lookup with an output schema and full schema coverage, the description covers action, optional filter, and result contents. The remaining gap is the undefined 'recent' window and result volume, which matters for planning calls but is minor given the tool's simplicity.

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 coverage is 100%, with both parameters documented including the CIK example, so the baseline is 3. The description restates that CIK identifies the company and that type filters filings, but adds no syntax, normalization, or defaulting detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search recent SEC filings for a company by CIK') and enumerates the returned fields, so the agent knows this is a filings lookup rather than a facts lookup. It does not explicitly contrast itself with the closely named sibling sec_xbrl_get_company_facts, leaving that differentiation to inference from the names.

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 by noting the type filter is optional, which tells the agent the minimal call is CIK-only. However, it gives no when-to-use versus alternatives (e.g., get_company_facts), no indication of how far back 'recent' extends, and no guidance on result limits or how to narrow oversized result sets.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.