Skip to main content
Glama

search_federal_register

Search Federal Register documents, including regulations and executive orders, by query to find relevant US legal materials.

Instructions

Search for documents in the Federal Register (regulations, executive orders, etc.). When TYPESAFE_API_KEY is set, only high-confidence Jev matches are returned.

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": "search_federal_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 50)
queryYesSearch query for regulations (e.g., 'environmental', 'healthcare', 'immigration')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one genuine behavioral trait — that setting TYPESAFE_API_KEY restricts results to high-confidence Jev matches — but says nothing about authentication requirements, rate limits, pagination, or what the result payload looks like. The 'Jev matches' term is also left undefined, so the agent cannot reason about what is being filtered out.

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?

Two short sentences, purpose front-loaded, with the conditional behavior placed second where it belongs. The only waste is the unexplained 'Jev matches' phrasing, which costs clarity without adding actionable meaning.

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 simple two-parameter read tool with no annotations and no output schema, the description establishes the corpus and one filtering caveat, which is close to adequate. However, against a crowded sibling set of legal/regulatory search tools, it leaves the routing decision and the return shape entirely unspecified.

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 both `query` and `limit` documented including the max-50 bound, so the schema does the heavy lifting. The description adds no syntax, format, or query-construction guidance beyond what the schema already states; baseline 3 applies.

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?

States a specific verb and resource: search for documents in the Federal Register, with parenthetical examples (regulations, executive orders). The corpus is clearly identified, which distinguishes it from generic siblings like search_all_legal, though it never explicitly contrasts itself with search_congress_bills, search_court_opinions, or get_recent_regulations.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this tool over the many sibling search tools, nor on when to prefer get_recent_regulations instead. The only conditional sentence concerns TYPESAFE_API_KEY filtering, which is a behavioral trait of the call rather than a selection rule.

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