Skip to main content
Glama
Sign In
The Stall

The Stall

by thebrierfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

federal-register-search

Search the Federal Register for rules, proposed rules, and notices by keyword. Returns title, abstract, document type, agencies, significance, effective date, and links. No API key required.

Instructions

Search the Federal Register for Rules, Proposed Rules, and Notices matching a keyword — returns title, abstract, document type, agencies, significance, effective date, and links. No API key. $0.002/call.

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
qNoSearch term or phrase (e.g. 'artificial intelligence', 'PFAS', 'cybersecurity').
typeNoFilter to a single document type (optional).
daysNoHow many calendar days back to search (default 90). Max 730.
limitNoMax documents to return (default 10, max 20).
significant_onlyNoIf true, return only documents flagged as significant by the issuing agency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided. Description discloses cost and no API key, plus return fields. However, lacks details on rate limits, pagination, error handling, or any destructive behavior.

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

Conciseness5/5

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

Two sentences, no filler. Front-loaded with verb. Every sentence adds value: purpose, return fields, cost, key requirement.

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?

Given no output schema and 5 parameters, the description covers return fields and key constraints. Could mention pagination or default behavior for limit, but still reasonably complete.

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% with good descriptions. The description adds context about return fields but does not significantly enhance parameter semantics beyond the schema.

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 clearly states the verb 'Search' and resource 'Federal Register' with specific document types (Rules, Proposed Rules, Notices). It is distinct from siblings like legal-search.

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?

Mentions no API key and cost per call, but does not specify when to use over alternatives or exclude conditions. Implicitly recommends for keyword search of Federal Register documents.

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

Deploy Server

Other Tools