Firecrawl MCP Server

Overview Schema Source Related Servers Discussions Admin

Firecrawl Government Index search

firecrawl_gov_search

Read-only

Search US federal, state, and local statutes, regulations, codes, and court opinions to answer legal or regulatory questions with primary text; clarify jurisdiction and as-of date when needed.

Instructions

Search US federal, state, and local statutes, regulations, codes, court opinions, and other government publications for legal or regulatory questions that need primary text. Clarify a missing jurisdiction or ambiguous as-of date before identifying the governing rule.

Optional filters narrow results by jurisdiction, court, court type, cited law or case, and site. Filters keep only pages the index has labeled, so a filtered search can leave out relevant pages, and no results does not mean none exist. Court labels are most complete for federal courts and case-law collections.

Returns ranked results with a position, title, URL, and matched snippet. Results may include historical versions, bill text, agency guidance, and third-party reproductions. Verify the issuer, jurisdiction, enacted/effective status, and version before citing current governing law. Read a known URL or additional page context with firecrawl_scrape. Use general search for non-US questions or missing coverage; no hits does not establish that no applicable law exists.

Input Schema

Name	Required	Description
`k`	No	Number of ranked results to return (default 10).
`cites`	No	Keep only pages that cite one law or case, as a printed citation such as "42 U.S.C. § 1983" or "5 U.S. 137", or a citation id such as "us:usc:42:1983".
`court`	No	Keep only pages labeled for one court, by CourtListener court id, such as "scotus", "ca9" or "nysd".
`query`	Yes	Natural-language legal or regulatory question or search phrase, including the jurisdiction, agency, or citation when relevant.
`domain`	No	Keep only pages from one site, such as "irs.gov".
`courtType`	No	Keep only pages from one type of court: federal-supreme, federal-appellate, federal-district, federal-bankruptcy, federal-special, military, state-supreme, state-appellate, state-trial, state-special, state-attorney-general.
`jurisdiction`	No	Keep only pages of one jurisdiction: "us" for federal, or "us-" plus a two-letter state or territory code, such as "us-ca" or "us-dc".

Output Schema

Name	Required	Description	Default
`results`	Yes	Ranked results, in the order the text block lists them.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.2Oct 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover only readOnly/openWorld/destructive, and the description adds substantial non-obvious behavior: filters keep only index-labeled pages so filtered searches can silently drop relevant results, court labels are most complete for federal courts, and results may include historical versions, bill text, agency guidance, and third-party reproductions. It also prescribes verification of issuer, jurisdiction, effective status, and version before citing.

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?

Front-loaded with purpose and scope, then filters, then returns, then verification and alternatives. Dense but nearly every sentence carries decision-relevant information; the results-verification block is slightly repetitive with the no-results warning.

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

Completeness5/5

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

Covers the full call lifecycle for a 7-parameter, open-world search tool: when to use, filter caveats, what comes back, how much to trust it, and where to go next. With annotations and an output schema already present, nothing material is missing.

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, but the description adds value beyond the schema by explaining that the optional filters narrow results and, critically, that filtering can exclude relevant pages. It does not add per-parameter syntax, but that detail is already fully carried by the schema.

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?

States a specific verb and resource ('Search US federal, state, and local statutes, regulations, codes, court opinions, and other government publications') and scopes it to legal/regulatory primary-text questions, which cleanly separates it from firecrawl_search and firecrawl_scrape.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use firecrawl_scrape for a known URL or more page context, and general search for non-US questions or missing coverage. It also states a pre-call behavior (clarify missing jurisdiction or ambiguous as-of date) and warns that no hits does not prove no applicable law exists.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.