Skip to main content
Glama

X420 agent services

x420_gov_federal-register

Read-onlyIdempotent

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. Price: $0.03 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: total, count, results[{document_number, title, type, publication_date, agencies, abstract, html_url, pdf_url}].

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 observed

TDQS

A4.4/5.0
Behavior5/5

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

Discloses behavior far beyond the annotations: the hosted tool does not pay and does not deliver results, it returns payment instructions (pay_to, network, price, x402 URL), costs $0.03 USDC on Base, and requires the x402 v2 handshake. Annotations (readOnlyHint true, idempotent, openWorld) are consistent with a non-mutating validation/search call.

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?

Front-loads the search capability and deliverable before the payment mechanics, so an agent can triage quickly. Slight redundancy between 'does NOT return the deliverable' and 'Deliverable once paid', plus boilerplate non-advice language, adds a little bulk but each block serves a distinct purpose.

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?

No output schema exists, yet the description enumerates the paid response shape (total, count, results[] with document_number, title, type, publication_date, agencies, abstract, html_url, pdf_url). Combined with the cost and x402 payment flow, nothing an agent needs to call it correctly 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 the schema already documents term, type, agency, and per_page including defaults and example values. The description adds nothing parameter-specific beyond restating the output shape; 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?

Opens with a specific verb and resource: full-text search of Federal Register documents, enumerating the document types (rules, proposed rules, notices, presidential documents) and sort order. This is unmistakably distinct from siblings like sec-edgar-company or usaspending-awards.

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 explicit operational guidance for the hosted variant: it validates input and returns payment instructions rather than results, then prescribes the exact sequence (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE) and names the local x420-mcp alternative for auto-pay. It does not state when to prefer this over sibling data sources, but the payment-path guidance is unusually concrete.

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