Lordevo Shop (x402 website checks)

US Federal Register search (rules, notices) ($0.002/call)

federal_register

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Public records] Searches US Federal Register documents (rules, proposed rules, notices, presidential documents) through the official FederalRegister.gov API: full-text term, optional agency slug, type and date range. Returns the total count and up to 20 documents with title, type, action, abstract, agencies, publication date, effective date, comment deadline (comments_open), docket IDs, RINs, citation and the HTML and official PDF links. Public-domain data, no key; cached 15 min. ~0.5-2 s.

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

Input Schema

Name	Required	Description	Default
`term`	Yes	Search words for Federal Register documents, 2-200 characters, e.g. stablecoin or "emission standards"
`type`	No	Document type: any (default), rule, proposed_rule, notice or presidential_document	any
`order`	No	Sort: newest (default), oldest or relevance	newest
`since`	No	Published on or after this date, YYYY-MM-DD
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`until`	No	Published on or before this date, YYYY-MM-DD
`agency`	No	Agency slug as used by FederalRegister.gov, e.g. securities-and-exchange-commission, environmental-protection-agency
`max_results`	No	Documents returned, 1-20 (default 10); total_count is always the full count	10

Output Schema

Name	Required	Description
`tool`	No
`cache`	No
`notes`	No
`query`	No
`_trial`	No	Present when the call was a free trial call.
`source`	No
`provider`	No
`returned`	No
`documents`	No
`price_usd`	No
`fetched_at`	No
`attribution`	No
`response_ms`	No
`total_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

AddedNov 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the bar is lower, but the description adds substantial operational context: x402/USDC-on-Base pricing at $0.002 per call, a 3-per-IP-per-UTC-day free trial, no API key requirement, 15-minute caching and 0.5–2 s latency. The only real gap is the 20-document result cap not being framed as a truncation risk alongside the total count.

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 definition is dense but front-loads the most decision-critical facts (price, trial, then what it searches) in a single tight paragraph. The pricing/trial repetition against the title and the parameter schema is mildly redundant, but nothing is genuinely 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?

For an 8-parameter search tool with an output schema, the agent has everything it needs: cost, free-trial path, latency, caching, auth-free access, and the content domain. Return fields are even summarized, which is more than the output schema alone requires.

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 parameter meaning is already fully documented and the baseline is 3. The description restates the searchable facets (full-text term, optional agency slug, type, date range) and notes 'up to 20 documents' plus that total_count is the full count, but adds no syntax or format detail the schema does not already give.

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 — 'Searches US Federal Register documents (rules, proposed rules, notices, presidential documents)' — through the named official API. An agent can immediately distinguish it from adjacent tools like sec_filings or page_markdown without opening the schema.

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 context is implied by the 'Public records' framing and the enumeration of searchable document types, and it usefully routes cost-sensitive callers to 'add trial: true or use try_free'. However, it never states when this tool is preferable to a sibling such as sec_filings, nor any when-not conditions, so guidance stays at the implied level.

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

All Lordevo Shop (x402 website checks) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?