Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Newest US Federal Register documents in one call: rules, proposed rules, notices or presidential documents with agencies

federal_register
Read-onlyIdempotent

Newest US Federal Register documents in one call: rules, proposed rules, notices or presidential documents with agencies, publication date, document number, abstract and link (type=RULE|PRORULE|NOTICE|PRESDOCU, count up to 50). One poll replaces watching the Federal Register. Pay per call $0.002 USDC on Base via x402.

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": "federal_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRULE, PRORULE, NOTICE or PRESDOCU
countNoup to 50
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description adds the critical behavioral fact that each call costs $0.002 USDC on Base via x402 and that the first call returns pricing. It does not state the default count value or pagination behavior, which leaves a small gap for a paid tool.

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?

The core capability is front-loaded in the opening clause, and the payment note is a short trailing sentence. The parenthetical is dense and the title largely duplicates the first sentence, but nothing is truly wasted.

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?

With three simple optional parameters, no output schema, and annotations covering safety, the description closes the loop by listing returned fields, the cost model, and the payment flow. An agent has everything needed to invoke it correctly.

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 coverage is 100%, and the description merely restates the enum values (type=RULE|PRORULE|NOTICE|PRESDOCU) and the count cap of 50 already documented in the schema. It adds no format or default detail beyond the structured fields, so 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?

The description names a concrete resource (US Federal Register documents) and enumerates the exact document types plus the fields returned (agencies, publication date, document number, abstract, link). No sibling tool overlaps this domain, so it is unmistakable what this tool retrieves.

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?

It gives a clear use case ('One poll replaces watching the Federal Register') and states the payment handshake ('omit on the first call to receive the price and payment requirements'). It does not spell out when-not-to-use, but there is no plausible competing sibling to route against.

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