Skip to main content
Glama

Search Federal Register documents by term or agency

law_federal_register
Read-only

Searches Federal Register documents via the official API (public domain). Filter by terms, agency slug, document type (rule, proposed rule, notice, presidential document) and date range. Each result includes title, document number, type, agencies, publication date, effective date, comment end date, abstract, and PDF/HTML URLs. limit max 50. Takes about 13 s; allow a 30 s timeout. Related tools on this server, for a different need: law_ecfr when you need to search or read US Code of Federal Regulations sections. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "law_federal_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeyword search terms (max 200 characters)
typeNoDocument type: RULE, PRORULE, NOTICE, PRESDOCU
limitNoMax results (1–50, default 20)
agencyNoAgency slug (e.g. securities-and-exchange-commission)
dateGteNoPublication date on or after (YYYY-MM-DD)
dateLteNoPublication date on or before (YYYY-MM-DD)

Output Schema

NameRequiredDescriptionDefault
countNo
totalNo
sourceNo
resultsNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the data source and public-domain status, the full result payload fields, the limit ceiling, an expected latency of ~13 s with a recommended 30 s timeout, and a per-successful-call price via x402 with failed calls free. Those cost and timing traits materially affect how an agent should call it.

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-loads purpose and filters, then result payload, then operational caveats (latency, price, sibling routing). No sentence restates the name or is filler; the pricing and timeout details are actionable rather than padding.

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?

For a zero-required-parameter search tool with a full schema and an output schema, the description covers the remaining unknowns: latency, timeout budget, cost model, and the alternative tool. Nothing an agent needs before calling 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 by translating document types into human labels (rule, proposed rule, notice, presidential document) that map onto the schema's RULE/PRORULE/NOTICE/PRESDOCU codes and by restating the limit ceiling. It does not explain the agency slug format beyond what the schema example shows.

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 (searches Federal Register documents), names the API source, and enumerates the filterable dimensions (terms, agency slug, document type, date range). It also distinguishes itself from the sibling law_ecfr by resource domain.

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?

Gives clear context: use this for Federal Register documents, and calls out law_ecfr explicitly for the different need of searching or reading CFR sections. It stops short of stating when not to use the tool or what to do when a query returns nothing, but the sibling routing is explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources