`reg_agency_agenda`

Pack: reginfo · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/reg_agency_agenda for the schema, then POST the same URL with its arguments for the data.

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.

Parameters

Name	Type	Required	Description
`agency`	string	yes	Agency 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).
`edition`	string	no	Edition YYYYMM. Defaults to the newest edition actually loaded.
`limit`	number,string	no	Max RINs to return (1-200, default 100).

Example call

Arguments

{
  "agency": "Department of Labor"
}

curl

curl -X POST https://gateway.pipeworx.io/reginfo/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"reg_agency_agenda","arguments":{"agency":"Department of Labor"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('reg_agency_agenda', {
  "agency": "Department of Labor"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the reginfo pack

{
  "mcpServers": {
    "reginfo": {
      "url": "https://gateway.pipeworx.io/reginfo/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

reg_agency_agenda