docket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REGULATIONS_GOV_API_KEY | No | A free Regulations.gov API key from api.data.gov. DEMO_KEY works for light use, but a personal key is recommended for higher rate limits. | DEMO_KEY |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingA | Report server health and configuration status without calling the API. Use this first if other tools fail: it tells you whether an API key is configured at all, which is the most common failure cause. |
| search_docketsA | Full-text search of federal rulemaking dockets on Regulations.gov. Returns docket summaries: id, title, docket_type (Rulemaking or Nonrulemaking), agency_id, last_modified, and match_context (a plain-text snippet showing why the docket matched). Use the returned id with get_docket for the abstract or list_documents for its documents. Args: query: Search terms, e.g. "artificial intelligence reporting". page: Result page, 1 to 20 (API limit; narrow the query instead of paging deeper). page_size: Results per page, 5 to 250. agency_id: Optional agency filter, e.g. "EPA" or "BIS". |
| get_docketA | Fetch one docket's full detail from Regulations.gov by its exact ID. Returns id, title, agency_id, docket_type, abstract (the docket's own summary of what the rulemaking does), keywords, rin (Regulation Identifier Number), and last_modified. Raises a not-found error for an ID that does not exist; get IDs from search_dockets rather than guessing them. Args: docket_id: Exact docket ID, e.g. "BIS-2024-0047". |
| list_documentsA | List the documents filed in one Regulations.gov docket. Returns document summaries: id, title, document_type (Proposed Rule, Rule, Notice, Supporting & Related Material, ...), posted_date, fr_doc_num (Federal Register document number), open_for_comment, comment_end_date, and withdrawn. A docket ID that matches nothing yields an empty list, not an error. Args: docket_id: Exact docket ID, e.g. "BIS-2024-0047". page: Result page, 1 to 20 (API limit). page_size: Results per page, 5 to 250. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct role: ping is health-only, search_dockets is the fuzzy query entry point, get_docket is exact-ID detail lookup, and list_documents returns child documents. The descriptions explicitly cross-reference IDs, so an agent should not confuse which tool to call.
The three data tools follow a clean verb_noun snake_case pattern: search_dockets, get_docket, list_documents. ping is a conventional health-check exception, but it is the only minor deviation and does not create confusion.
Four tools are well-scoped for a docket-browsing server: health check, search, detail lookup, and document listing. There is no redundancy, and the count fits comfortably within an appropriate MCP server size.
The core docket workflow is covered end-to-end: search dockets, fetch full docket details, and list the documents within a docket. The main gap is the absence of a per-document detail/search tool, so deeper document-level retrieval is not possible.