Skip to main content
Glama

legal_gov_search

Search US federal, state, and local law—statutes, regulations, court opinions, bills, and ordinances—and get citation-backed government source links with quoted text for AI agents.

Instructions

Search US law for AI agents — statutes, regulations, court opinions, bills, county and city ordinances — via Firecrawl's Government & Legal Index (30M+ data points from government sites). Free. Every result carries its government source link and quoted text so answers stay citation-backed. Covers US federal, state and local law; other countries are not in this index.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "legal_gov_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/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 delivers real behavioral facts: the tool is free, results include government source links and quoted text, and coverage is limited to US federal/state/local. Gaps remain — no mention of result count, pagination, latency, or whether an empty query is meaningful — but the citation-backing guarantee is the key behavioral disclosure an agent needs.

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?

Front-loaded with the action and resource, then the index provenance, then the coverage caveat — each clause adds distinct information (cost, citation behavior, geographic limit). No filler or restatement of the name.

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 one-parameter search tool with no annotations and no output schema, the description covers data source, scope, cost, and return characteristics, which is most of what an agent needs. The one real omission is how to construct the query string, which matters precisely because the schema offers zero help there.

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 0% for the single 'query' parameter, so the description must compensate and largely does not. It implies natural-language topical search ('Search US law for AI agents') but never states whether the query should be keywords, a citation, a statute name, or a question, nor any length or syntax constraints.

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 ('Search') and resource ('US law') and enumerates the covered document types — statutes, regulations, court opinions, bills, county and city ordinances — plus the underlying index (Firecrawl Government & Legal Index, 30M+ points). It is unmistakable against the sibling list, which is entirely crypto/arena/agent-infrastructure tooling with no other legal search.

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

Usage Guidelines4/5

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

Explicitly frames the use case ('Search US law for AI agents') and states a hard exclusion: other countries are not in this index. That is a genuine when-not signal. No alternatives are needed since no sibling competes for this task, but there is no guidance on query phrasing or on when the index would be the wrong source (e.g. non-authoritative legal advice).

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