Skip to main content
Glama

Kempt Horizon Data Toolkit

SEC company filings

sec_company_filings
Read-only

Recent SEC filings (10-K, 10-Q, 8-K, ...) for a company with document URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
cikNoSEC CIK, e.g. 320193
formsNoForm types, e.g. 10-K,10-Q,8-K
limitNo
dateToNoYYYY-MM-DD
tickerNoStock ticker, e.g. AAPL
dateFromNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds useful return context by noting document URLs are included, but it says nothing about pagination, recency ordering, or that identifiers must resolve to a company - gaps that matter for an open-world lookup.

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?

A single front-loaded sentence with no filler, and the form types and URL return are packed efficiently. It is arguably too terse for a six-parameter tool, but nothing is wasted.

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?

With 6 optional parameters and no output schema, the description should clarify the minimum viable invocation, and it does not say that at least one of cik or ticker is needed. That is the main missing piece; otherwise the resource, form types, and return shape are covered.

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 83%, with cik, ticker, forms, dateFrom and dateTo documented inline, so the baseline of 3 applies. The description's 'recent' hints at limit/sort behavior but does not clarify whether forms accepts a comma string vs array or that zero parameters are required.

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?

The description names a specific resource (SEC filings for a company), enumerates the common form types, and notes that document URLs are returned. It is clear what the tool does, but it does not differentiate itself from the sibling sec_filing_search or sec_company_financials, so an agent must infer that this is company-scoped retrieval rather than keyword search.

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?

Usage is only implied: 'for a company' and 'recent' suggest company-scoped, recency-ordered retrieval, but the description never states when to prefer this over sec_filing_search or sec_company_financials, nor any prerequisites (e.g., needing a CIK or ticker).

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.

Resources