Regulations Gov

Search Dockets

search_dockets

Read-onlyIdempotent

Search regulatory dockets. Filter by free-text query, agency (acronym like "EPA", "FDA"), docket type (Rulemaking / Nonrulemaking), or date range. Returns dockets with title, agency, type, status, document counts.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Full-text search
`agency`	No	Agency acronym (e.g., "EPA", "FDA", "DOT")
`page_size`	No	5-250 (default 25)
`docket_type`	No	Rulemaking \| Nonrulemaking
`page_number`	No	1-based page
`last_modified_to`	No	YYYY-MM-DD HH:MM:SS or YYYY-MM-DD
`last_modified_from`	No	YYYY-MM-DD HH:MM:SS or YYYY-MM-DD

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Current page number
`total`	Yes	Total number of dockets matching the query
`results`	Yes	List of docket objects with metadata
`returned`	Yes	Number of results in this response
`page_size`	Yes	Number of results per page
`total_pages`	Yes	Total number of pages

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "agency": "EPA",
+    "docket_type": "Rulemaking",
+    "query": "emissions standards"
+  },
+  {
+    "agency": "FDA",
+    "last_modified_from": "2024-01-01",
+    "last_modified_to": "2024-12-31",
+    "page_size": 50
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "page_size": {
+      "description": "Number of results per page",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "List of docket objects with metadata",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "description": "Docket ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Resource type",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of results in this response",
+      "type": "integer"
+    },
+    "total": {
+      "description": "Total number of dockets matching the query",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "total_pages": {
+      "description": "Total number of pages",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "total",
+    "page",
+    "page_size",
+    "total_pages",
+    "returned",
+    "results"
+  ],
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by enumerating filter types and the exact fields returned (title, agency, type, status, document counts), which supplements the annotations without contradicting them.

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 concise sentences, front-loaded with the core action, and then dense with relevant details about filters and returns. No redundant phrases or filler.

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 a rich output schema and full parameter documentation, this description covers the essential purpose, filters, and return shape adequately. It does not mention open-world behavior or pagination, but those are either annotated or captured by the schema, so the overall context is sufficient.

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 schema already documents all seven parameters. The description restates agency and docket_type semantics but does not add meaningful detail beyond the schema, such as pagination behavior or date format specifics.

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 uses a specific verb ('Search') and resource ('regulatory dockets'), followed by concrete filtering dimensions and return fields. It clearly distinguishes from sibling tools like search_comments and get_docket by targeting dockets specifically.

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?

The description clearly indicates this is for searching regulatory dockets with optional filters, giving a clear use context. However, it does not explicitly state when to prefer this over search_comments or search_within, so no exclusions or alternatives are mentioned.

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

All Regulations Gov tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.