Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sec_full_text_search

Search full text of SEC EDGAR filings by query, form type, and date range, with pagination, avoiding paid full-text search tiers.

Instructions

Full-text search across EDGAR filings. Searches the full text of SEC EDGAR filings, filtered by form and date, with pagination. Free where incumbents gate full-text search behind paid tiers.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query (supports quoted phrases)
toNoLatest filing date (YYYY-MM-DD)
fromNoEarliest filing date (YYYY-MM-DD)
pageNo1-based page number, default 1
formsNoFilter by form types, comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

B3.1/5.0
Behavior2/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, yet it only adds 'with pagination' (already covered by the schema's page parameter) and a marketing claim about being free. Nothing is said about rate limits, result-size caps, authentication, or ordering, which materially affects how an agent should invoke it.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, but the second sentence largely restates it ('Searches the full text of SEC EDGAR filings...') and the third is promotional copy about paid-tier competitors that does not help an agent call the tool. Two of three sentences add little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter search tool with no annotations and no output schema, the definition covers the what but not the when or the behavioral envelope. Schema coverage compensates on parameters, but the absence of usage routing and return-shape context leaves it only adequate.

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% with five documented parameters, so the baseline is 3. The description's references to form and date filtering and pagination merely restate what the schema already declares, adding no syntax, format, or edge-case detail beyond it.

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 opening sentence states a specific verb and resource ('Full-text search across EDGAR filings'), which cleanly separates it from sibling tools like sec_company_search or sec_filing that operate on specific companies or filings. However, it never names those siblings or contrasts the full-text retrieval model against them, so differentiation is implicit rather than explicit.

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?

Mentioning that results are 'filtered by form and date' implies the use case (locate filings by language rather than by company), which is the minimum viable guidance. There is no explicit when-to-use statement, no exclusions, and no routing advice toward sec_company_search or sec_filing for non-full-text lookups.

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