Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_sec_companies_financials

Retrieve a SEC company's financial-statement history by CIK, covering income, balance sheet, and cash flow, newest fiscal year first.

Instructions

Get a SEC company's financial-statement history. Returns a company's 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 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

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the empty-series-not-404 convention, the newest-fiscal-year-first ordering, and the shape of lines/ratios keys. It omits auth requirements and any explicit rate-limit behavior, keeping it below a 5.

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?

Purpose is front-loaded and the rest is dense, useful detail about return shape and edge cases. Minor waste in the near-duplicate opening ('Get a SEC company's financial-statement history. Returns a company's financial-statement history...'), but overall tight for the amount of information conveyed.

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 6-parameter tool with no output schema and no annotations, the description compensates well by explaining the returned lines/ratios keys, the ordering, and the empty-result semantics. It does not fully describe the output envelope or pagination interaction with limit, leaving a small gap.

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 all six parameters are already documented (including the from/to fiscal_year bounds and limit cap). The description only restates the statement and period enums, which the schema already provides; the lines/ratios key detail describes the response rather than the inputs, so net added parameter value is small — baseline 3.

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 — 'Get a SEC company's financial-statement history' — and names the report types (income statement, balance sheet, cash flow). It implies a distinction from the live '/sec/financials' endpoint and the datasets_sec_companies_* family via the 'dataset' framing, but never explicitly contrasts itself with the sibling sec_financials tool.

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?

No explicit when-to-use or when-to-prefer-an-alternative guidance. The note that unknown CIKs and non-XBRL filers return an empty series instead of a 404 implicitly tells the agent when to expect nothing back, which is useful context, but it stops short of routing between siblings.

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