Skip to main content
Glama

Reg Agency Agenda

reg_agency_agenda
Read-onlyIdempotent

One agency's full regulatory agenda for a given (or the newest) edition, every RIN it has open, grouped by rule_stage. Answers "what is EPA's regulatory agenda", "how many rules does DOL have in the proposed stage". Use reg_agenda_search instead when filtering by keyword or across agencies.

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": {
      "agency": "Department of Labor"
    },
    "name": "reg_agency_agenda"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax RINs to return (1-200, default 100).
agencyYesAgency name, acronym, or code, e.g. "EPA", "Department of Labor", "1200". Matched case-insensitively against name/acronym/code, and against the PARENT agency (so a sub-agency's rules are included when you ask for the parent).
editionNoEdition YYYYMM. Defaults to the newest edition actually loaded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds meaningful behavior beyond them: results are grouped by rule_stage and the edition defaults to the newest loaded. It does not state what happens when an agency match is ambiguous or missing, which is the only notable gap.

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?

Three tight sentences with no filler: scope first, example questions second, sibling routing last. Every sentence carries information an agent needs to choose and call the tool.

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 compensates by stating the return shape (all open RINs grouped by rule_stage) and the edition default. For a three-parameter read tool with full annotation coverage, it is complete enough to call correctly; only edge-case behavior for unmatched agencies is unaddressed.

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%, so the baseline is 3. The description only loosely reinforces the edition default ('newest') and does not add syntax, matching rules, or limit semantics beyond what the schema already documents.

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?

Names a specific resource (one agency's full regulatory agenda for an edition), the unit returned (every open RIN, grouped by rule_stage), and explicitly contrasts with reg_agenda_search. An agent can distinguish it from the sibling without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides both a positive use case (per-agency agenda questions like 'what is EPA's regulatory agenda') and an explicit exclusion routing to reg_agenda_search for keyword or cross-agency queries. Nothing is left to inference.

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.