Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sec_financials

Retrieve normalized income statement, balance sheet, or cash flow data from SEC EDGAR filings by CIK or ticker, resolving inconsistent XBRL tags into a stable schema.

Instructions

Normalized income statement, balance sheet, or cash flow. Returns a company's normalized financial statements across recent periods, resolving EDGAR's inconsistent XBRL tags to a stable schema. Provide cik or ticker. Credential-free public SEC data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoSEC CIK (numeric or zero-padded)
limitNoNumber of periods, default 5, max 20
periodNoPeriod basis, default annual
tickerNoTicker symbol (alternative to cik)
statementNoStatement, default income

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.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does reasonably well: it discloses the normalization behavior, the multi-period scope, and the lack of credential requirements. It does not detail response shape or error behavior, but for a read-only retrieval tool the disclosed traits are substantive.

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

Conciseness5/5

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

Three tight sentences: the first states the resource and output, the second explains the normalization value and identifier options, and the third covers access. No filler or redundancy; the most important information is front-loaded.

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 no output schema and no annotations, the description gives enough context to call it correctly: what statements are available, the normalization behavior, the identifier options, and the credential-free nature. It could describe the return shape more explicitly, but the core invocation context is complete.

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 adds value by stating 'Provide cik or ticker,' clarifying that these identifiers are alternatives, and 'across recent periods,' which ties to the limit parameter. This goes beyond the individual field descriptions.

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 names specific resources ('income statement, balance sheet, or cash flow') and a precise verb ('Returns'), and clarifies the tool's unique value: normalizing EDGAR's inconsistent XBRL tags into a stable schema. This distinguishes it from raw SEC filing and other financial-data sibling tools.

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 when to use the tool — when normalized financial statements are needed — and adds practical context like 'Provide cik or ticker' and 'Credential-free public SEC data.' However, it does not explicitly name alternatives or state when not to use it versus sibling SEC/financial tools.

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