Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_sec_companies_financials

Retrieve a company's normalized financial-statement history from SEC filings, including income statement, balance sheet, and cash flow with derived ratios, by CIK. Filter by fiscal year and period for precise analysis.

Instructions

Get a SEC company's financial-statement history. Returns a company's normalized financial-statement history (income statement, balance sheet, cash flow) from the SEC companies dataset, newest fiscal year first. An unknown CIK or a company with no XBRL data returns an empty series rather than a 404 — most filers without a current ticker have no financial-statement history at all. lines keys are the same normalized concept names the live /sec/financials endpoint uses (e.g. revenue, net_income, total_assets); ratios keys include gross_margin, operating_margin, net_margin, revenue_growth_yoy, current_ratio, debt_to_equity, free_cash_flow where derivable. statement enum: income, balance, cash_flow. period enum: annual, quarterly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoInclusive upper bound on fiscal_year
cikYesSEC CIK, numeric or zero-padded
fromNoInclusive lower bound on fiscal_year
limitNoMaximum points returned (most recent fiscal years first), default 100, max 400
periodNoPeriod-type enum: annual, quarterly. Omit to return both.
statementNoStatement enum: income, balance, cash_flow. Omit to return all three.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / period / enum
      Added value: +[
+  "annual",
+  "quarterly"
+]
    • addedInput schema / properties / statement / enum
      Added value: +[
+  "income",
+  "balance",
+  "cash_flow"
+]
  2. Addedv1.6.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It is thorough: it explains the empty-series behavior for unknown CIKs or companies with no XBRL data, notes that most filers without a current ticker have no history, describes the response structure (lines and ratios with specific key examples), and states the ordering. This goes well beyond a minimal description and leaves little ambiguity about what the tool does in edge cases.

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?

The description is relatively long but every sentence contributes value: purpose, behavior, key structure, and enums. It is front-loaded with the main purpose and then provides necessary specifics. It is well-structured and not verbose, though it could be considered slightly dense.

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 tool with six parameters and no output schema, the description covers a substantial amount: return type, ordering, edge cases, key names, and enums. The only minor gap is that it doesn't fully describe the overall response shape beyond the keys, but this is mitigated by the absence of an output schema and the richness provided elsewhere. It is largely complete for an agent to call correctly.

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 already documents all six parameters with descriptions. The description adds marginal value on parameters: it reiterates the enums for statement and period, but does not provide additional meaning beyond the schema. For example, it doesn't explain how to/from interact or clarify the limit default beyond what's in the schema. Baseline 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 opens with a clear verb and resource: 'Get a SEC company's financial-statement history.' It then specifies what is returned (income statement, balance sheet, cash flow), the dataset source, and the ordering (newest fiscal year first). This clearly distinguishes it from sibling tools like the live /sec/financials endpoint by noting it is from the SEC companies dataset.

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 provides helpful context about the tool's behavior (returns empty series for unknown CIK, etc.) and mentions the live /sec/financials endpoint, but it never explicitly states when to use this dataset tool versus alternatives such as sec_financials or datasets_sec_companies_item. The usage guidance is implied rather than explicit, so an agent would need to infer the appropriate context.

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