Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sec_company_submissions

List recent SEC EDGAR filings for a company using CIK or ticker; filter by form type and date range and get document URLs and profile details.

Instructions

List a company's EDGAR filings. Returns a company's recent SEC filings (form, dates, primary document URL) filtered by form type and date range, plus company profile fields as reported by EDGAR: entity_type, former_names, exchanges, category, fiscal_year_end, state_of_incorporation. Provide cik or ticker.

Input Schema

NameRequiredDescriptionDefault
toNoLatest filing date (YYYY-MM-DD)
cikNoSEC CIK (numeric or zero-padded)
formNoFilter by form type, e.g. 10-K, 10-Q, 8-K
fromNoEarliest filing date (YYYY-MM-DD)
limitNoMax filings, default 50, max 500
tickerNoTicker symbol (alternative to cik)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral burden. It discloses the return shape (form, dates, primary document URL, profile fields) and the filter semantics, but says nothing about ordering, pagination behavior, or what happens when neither cik nor ticker is supplied. Adequate but with clear gaps for an unannotated tool.

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 sentences, front-loaded with the core action, then return contents, then the identifier requirement. Dense but every clause carries information; the field enumeration is long but justified given no output schema.

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?

No output schema exists, so the description compensates by listing returned fields, and for a read-only EDGAR listing with 100% schema coverage the remaining gaps (ordering, failure modes) are minor. It stops short of fully covering behavioral edge cases for an unannotated tool.

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

Parameters4/5

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 earns above baseline by surfacing the one constraint the schema does not express (that cik or ticker must be provided despite no required fields) and by framing form/from/to as filters rather than raw fields.

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 ('List a company's EDGAR filings') and enumerates both the filing fields and profile fields returned, so the agent knows exactly what it gets. It does not name or distinguish itself from siblings like sec_filing or sec_company_search, which keeps it from a 5.

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 closing 'Provide cik or ticker' gives a required-input hint (notably, the schema marks no parameters as required). However, there is no guidance on when to choose this over sec_filing, sec_company_search, or sec_financials, leaving alternatives to inference.

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

Deploy Server

Other Tools