Skip to main content
Glama

Reg Agenda Search

reg_agenda_search
Read-onlyIdempotent

Search the Unified Agenda of federal regulatory actions, every rule an agency has told OIRA it plans to propose, finalize, or has completed, since Fall 1995. Answers "what rules is EPA planning", "regulatory agenda for immigration", "upcoming FDA rulemaking on menthol cigarettes". Filter by agency (name, acronym, or code, e.g. "EPA", "Environmental Protection Agency"), a keyword against the rule title/abstract, and/or rule_stage (e.g. "Proposed Rule Stage", "Final Rule Stage", "Prerule Stage", "Long-Term Actions", "Completed Actions"). Defaults to the newest edition on file when edition is omitted. This is the LEADING record, an intent shows up here, often years before the same rule appears in eCFR or the Federal Register.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25,
      "agency": "EPA"
    },
    "name": "reg_agenda_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax RINs to return (1-100, default 25).
stageNoRestrict to one rulemaking stage, e.g. "Proposed Rule Stage", "Final Rule Stage", "Prerule Stage", "Long-Term Actions", "Completed Actions". Substring match.
agencyNoAgency name, acronym, or code, e.g. "EPA", "Environmental Protection Agency", "2000". Matched case-insensitively against name/acronym/code, and against the PARENT agency too (so "Interior" matches its sub-agencies).
editionNoRestrict to one edition, YYYYMM (e.g. "202504"). Defaults to the newest edition actually loaded.
keywordNoFree-text match (case-insensitive) against the rule title and abstract, e.g. "menthol", "PFAS", "overtime".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely useful behavioral context: it only covers the newest edition unless overridden, and the agenda is a leading indicator that may precede eCFR/Federal Register records by years. It says nothing about pagination, result ordering, or what happens when filters match nothing.

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 the core purpose, then filters, then default behavior, then the temporal-lead positioning sentence. The long appositive describing the agenda is informative rather than filler, though the description is on the dense side and the multi-clause parentheses slow scanning.

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?

With no output schema, the description does enough to convey what a result represents (a planned or completed regulatory action, its stage, agency, and edition) and the temporal caveat about leading records. It doesn't describe the result fields or pagination behavior, but for a five-optional-parameter search tool with full schema coverage it is largely 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 description coverage is 100%, so the baseline is 3; the description mostly restates what the schema already says about agency, stage, and keyword filtering. It adds minor value by giving agency-match examples and noting the default edition, but also introduces a naming inconsistency by referring to "rule_stage" while the actual parameter is "stage", which could confuse an agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search the Unified Agenda of federal regulatory actions") with its historical scope ("since Fall 1995") and concrete example questions. It positions itself relative to external corpora (eCFR, Federal Register) but does not distinguish itself from close siblings like reg_agency_agenda or reg_agenda_coverage, so it stops just short of a 5.

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 clear usage context through natural-language question examples ("what rules is EPA planning", "upcoming FDA rulemaking on menthol cigarettes") and shows how filters compose. It also states the default behavior when edition is omitted. There is no explicit when-not or named-alternative guidance against sibling agenda tools.

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.