Skip to main content
Glama

x420_gov_federal-register

Search Federal Register documents by term, type, or agency to retrieve newest-first rules, proposed rules, notices, and presidential documents with abstracts and official links.

Instructions

Federal Register search: Full-text search of Federal Register documents (rules, proposed rules, notices, presidential documents) newest first, with abstracts and links, from the Federal Register API (free, no key). Source: federalregister.gov. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.03 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: total, count, results[{document_number, title, type, publication_date, agencies, abstract, html_url, pdf_url}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"term":"roofing","per_page":"1"}.

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": {
      "term": "<term>"
    },
    "name": "x420_gov_federal-register"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYessearch phrase
typeNorule, prorule, notice or presdocu (default: all)
agencyNoagency slug, e.g. environmental-protection-agency (default: all)
per_pageNo1–20 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.8/5.0
Behavior4/5

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

Adds substantial context annotations do not carry: a concrete price ($0.03 USDC per call), settlement chain and mechanism (Base via x402), the wallet environment variable required for payment, and the presence of a signed receipt plus settlement transaction in the response. That is exactly the kind of cost/auth/return behavior an agent needs before spending real money. It stops short of five because it never states rate limits, failure/refund behavior if the upstream call fails, or how pagination works beyond per_page.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and scope are front-loaded, which is good, but the block is dense and padded: 'Source: federalregister.gov' duplicates the name, and the 'Not professional, legal, insurance, engineering, medical, financial or tax advice' disclaimer consumes a full sentence without helping tool selection. The pricing, returns, and example sections do earn their place.

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 four-parameter search with no output schema, the description is unusually complete: it enumerates the returned JSON fields, discloses paid settlement and receipts, and gives a concrete example input. The remaining gap is retrieval mechanics — with per_page capped at 20 and no page/offset parameter, the description should say how to reach results beyond the first 20 given that a 'total' count is returned.

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 four parameters (term, type, agency, per_page) are already documented with defaults in the schema. The description only restates a sample call ({"term":"roofing","per_page":"1"}), which illustrates shape but adds no semantics beyond what the schema already provides. Baseline 3 applies.

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 ('Full-text search of Federal Register documents') and enumerates the document types covered (rules, proposed rules, notices, presidential documents), plus sort order and result contents. An agent can distinguish this from x420_gov_sec-edgar-company or x420_gov_usaspending-awards based on the named corpus alone.

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?

Usage is implied by the domain naming rather than stated: it never says when to choose this over the SEC EDGAR or USAspending siblings, nor does it give exclusions. It does clarify defaults ('default: all' for type and agency) via the schema and implies full-text regulatory lookup, which is enough to infer intent but not to route confidently among related government-data tools.

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