Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

US Federal Register search: new rules, proposed rules and notices by topic, agency and date, with comment deadlines

federal_register_search
Read-only

Search the US Federal Register, the government's daily journal of rules, proposed rules, notices and presidential documents. Filter by keyword, type, agency and date range, only items still open for comment, or look up one document by number. Returns title, agency, publication and effective dates, comment deadline, a trimmed abstract, citation, docket IDs and official links. Useful for agents that monitor regulation. Not charged for invalid input or when nothing matches. Paid via x402; see list_prices.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional: rule, proposed_rule, notice or presidential.
limitNoHow many results, 1 to 25 (default 10).
queryNoOptional keyword or phrase, e.g. "lead pipes".
sinceNoOptional: published on or after this date (YYYY-MM-DD).
untilNoOptional: published on or before this date (YYYY-MM-DD).
agencyNoOptional: agency slug, e.g. "environmental-protection-agency".
commentsOpenNoOptional: only items whose public comment period is still open.
documentNumberNoOptional: look up one document by its Federal Register number instead of searching.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-schema behavior: the shape of the return payload (title, agency, dates, comment deadline, abstract, citation, docket IDs, links) and, importantly, the billing policy ('not charged for invalid input or when nothing matches' and 'paid via x402; see list_prices'), which an agent must know before calling.

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-loaded with purpose, then filters, then return payload, then use case, then billing — a logical progression with no filler sentences. The 'useful for agents that monitor regulation' line is slightly generic, but the billing lines earn their place by affecting invocation decisions.

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 no output schema, the description carries the burden of describing return values and does so concretely. It also covers the two invocation modes, all filter dimensions, and the cost model, leaving nothing an agent needs in order to call it correctly unstated.

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 each of the 8 optional parameters is already documented with examples in the schema. The description names the filter families but adds no syntax, format, or precedence detail beyond what the schema provides, 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?

States a specific verb (search) and a specific, uniquely named resource (the US Federal Register), then enumerates the content types it covers (rules, proposed rules, notices, presidential documents). No sibling tool overlaps this domain, and an agent can tell instantly what it 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?

The description lays out the two operative modes — multi-filter search (keyword, type, agency, date range, commentsOpen) versus single-document lookup by number — and names a use case (regulation monitoring), which gives clear context for selection. It stops short of explicit exclusions or 'when not to use' guidance, so it falls just under a 5.

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

All VerifyLite toolsInspect
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