Skip to main content
Glama

federal-regulations-mcp-server

by io.github.cyanheads

regulations_search_rules

regulations_search_rules
Read-only

Search the Federal Register — the daily journal of US proposed rules, final rules, notices, and presidential documents (1994–present) — filtering by full-text query, document type, agency slug, publication date range, and whether the rule is open for comment. The primary discovery entry point: results carry the document number (open with regulations_get_document), docket IDs, RINs, and affected CFR parts that chain into the comment and codified-text tools. The Federal Register caps navigation at 50 pages and the match count at 10,000; when a result set is larger, narrow with published_after/published_before rather than paging deeper.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1–50, default 1). The FR API caps total_pages at 50 — with per_page=100 this allows navigating up to 5,000 results. To reach beyond that window, narrow with published_after/published_before rather than paging deeper.
typeNoDocument types to include. PRORULE=Proposed Rule, RULE=Final Rule, NOTICE=Notice, PRESDOCU=Presidential Document. Omit for all types.
queryNoFull-text search across document title and body. Omit to browse by filters alone (e.g. all EPA proposed rules in a date range).
agenciesNoFilter to one or more agencies by Federal Register agency slug (e.g. "environmental-protection-agency", "securities-and-exchange-commission"). Slugs are the kebab-case agency name; if unsure, search by query and read the agency slugs off the results.
per_pageNoResults per page (2–100, default 20). The Federal Register API treats exactly 1 as its default page size instead of returning one result.
published_afterNoEarliest publication date, ISO 8601 (YYYY-MM-DD). Combine with published_before to window large result sets — the FR caps navigation at 50 pages.
published_beforeNoLatest publication date, ISO 8601 (YYYY-MM-DD).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
shownNoResults returned on this page.
noticeNoGuidance when nothing matched or when results were truncated.
resultsNoMatching Federal Register documents (this page).
truncatedNoTrue when matches exceed the FR 50-page (5,000-record) navigation ceiling.
totalCountNoTotal matches before pagination (FR count; capped at 10,000 by the API window).

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a read-only, open-world tool, and the description adds valuable behavioral detail beyond that: the Federal Register caps navigation at 50 pages and match count at 10,000, and results chain into downstream tools. This gives agents the necessary context on pagination limits and result composition without waiting for a failure.

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?

The description is about 110 words, and every sentence earns its place: purpose, chaining value, and a concrete limitation. It is front-loaded with the core functionality, then adds behavioral and usage nuances without fluff.

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?

Given the tool's moderate complexity and the presence of an output schema, the description covers the essentials: result fields (document number, docket IDs, RINs, affected CFR parts), how results connect to comments and codified-text tools, and how to handle large result sets. Nothing critical for an agent to invoke this correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Though schema description coverage is 100%, the description falsely claims a filter 'whether the rule is open for comment' that is not present in the schema, misleading agents into thinking such a filter exists. This outweighs the baseline benefit of high schema coverage and actually harms parameter semantics.

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 description clearly identifies a specific verb ('Search') and resource (the Federal Register), and differentiates itself as 'the primary discovery entry point' with chains to sibling tools. However, it incorrectly claims filtering by 'whether the rule is open for comment,' a filter that does not exist in the schema, slightly muddying the otherwise precise scope.

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?

The description provides clear context for when to use the tool—as the primary discovery endpoint—and points to the related tool 'regulations_get_document' for following document numbers. It does not explicitly exclude alternatives or give when-not-to-use guidance, but the mention of chaining and pagination guidance gives agents a clear sense of when to use this versus the rest of the workflow.

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

All federal-regulations-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: browsing vs searching, getting specific entities (CFR sections, dockets, documents) vs listing/finding comments. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the consistent 'regulations_<verb>_<object>' pattern (e.g., browse_cfr, get_docket, list_open_comments), making it easy to predict functionality.

Tool Count5/5

Seven tools is well-scoped for a regulations domain, covering discovery (search, browse, list) and retrieval (get, find) without redundancy or bloat.

Completeness5/5

The set covers the core regulatory workflow: searching rules, browsing CFR structure, retrieving specific sections, dockets, documents, and comments. No obvious gaps for read-only access.

Resources