Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sec_frames

Retrieve every filer's reported value for one XBRL concept in a single reporting period to compare cross-company financial data from EDGAR frames.

Instructions

Cross-company values for one XBRL concept and period. Returns every filer's reported value for one XBRL concept in one reporting period (an EDGAR "frame").

Input Schema

NameRequiredDescriptionDefault
unitNoUnit of measure, default USD
limitNoMax companies, default 200, max 2000
periodYesReporting frame, e.g. CY2024, CY2024Q1, CY2024Q4I
conceptYesXBRL concept tag, e.g. Assets, Revenues
taxonomyNoXBRL taxonomy, default us-gaap

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / taxonomy / enum
      Added value: +[
+  "dei",
+  "ifrs-full",
+  "srt",
+  "us-gaap"
+]
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully describes what is returned (all filers' values for one concept/period), but says nothing about pagination behavior, the default cap of 200, ordering, or permissions. It adds conceptual value but leaves operational traits to the schema.

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?

Two tight sentences, zero waste, with the core scope (cross-company, one concept, one period) front-loaded and the EDGAR frame gloss placed where it clarifies rather than pads.

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 five-parameter tool with full schema coverage and no output schema, the description adequately conveys the return semantics (per-filer values for a single concept/period). Missing only operational details like pagination and the practical meaning of the limit cap, which are minor here.

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 five parameters including examples and defaults. The description reinforces the one-concept/one-period constraint but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 states a specific resource and scope: cross-company reported values for one XBRL concept and one period. The phrase 'every filer's reported value' and the gloss 'an EDGAR frame' make the resource concrete. It does not explicitly name sibling tools, so it stops short of full differentiation.

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 implied by 'cross-company' and 'every filer's reported value', which suggests a market-wide screen rather than a single-company lookup, but there is no explicit when-to-use statement or named alternative (e.g. sec_financials, sec_company_intelligence). The agent must infer the choice.

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