Skip to main content
Glama

Federal Register Search - US rules, proposed rules, notices

federal_register
Read-onlyIdempotent

Search the official US Federal Register: final rules, proposed rules, notices and presidential documents with abstract, agencies, publication date and links. Filter by keyword, type, agency and date. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/federal-register.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "RULE",
      "query": "artificial intelligence",
      "maxItems": 10
    },
    "name": "federal_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRULE, PRORULE, NOTICE or PRESDOCU
orderNonewest or relevancenewest
queryNoKeywords, e.g. artificial intelligence
sinceNoPublished on or after (YYYY-MM-DD)
agencyNoAgency slug, e.g. environmental-protection-agency
maxItemsNoMax results (1-50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, but the description adds genuinely new context: free tier of 25 calls/day per IP and a paid path at $0.005 per call via x402, plus the fact that results include abstracts, agencies, dates and links. It does not discuss pagination or result caps beyond what the schema states.

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?

Three short sentences, front-loaded with what is searched and what comes back, then filtering, then access/pricing terms. No filler or repetition; every sentence carries information an agent needs.

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 read-only search tool with full schema coverage and no output schema, the definition covers the resource, the return fields, filtering dimensions and the cost model. Nothing essential to correct invocation is missing.

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%, so all six parameters (type, order, query, since, agency, maxItems) are already documented in the schema including enums and defaults. The description's "filter by keyword, type, agency and date" adds only a high-level echo of those fields, which fits the baseline 3.

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?

The description names a specific verb and resource ("Search the official US Federal Register") and enumerates the document types covered (final rules, proposed rules, notices, presidential documents) plus the fields returned. This is clearly distinct from sibling tools like literature_search or clinical_trials, so an agent can select it without ambiguity.

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

Usage Guidelines3/5

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

"Filter by keyword, type, agency and date" implies how to narrow results but gives no explicit when-to-use or when-not-to-use guidance and names no alternative. Usage is inferable from the regulatory-search framing rather than stated outright.

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