Regulations Gov

Search Comments

search_comments

Read-onlyIdempotent

Public comments filed on a docket or document. Filter by docketId, documentId (e.g., "EPA-HQ-OAR-2021-0317-0001"), free-text, or date.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Free-text query
`docket_id`	No	Filter to a docket
`page_size`	No	5-250
`posted_to`	No	YYYY-MM-DD
`document_id`	No	Filter to a single document
`page_number`	No	1-based page
`posted_from`	No	YYYY-MM-DD

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Current page number
`total`	Yes	Total number of comments matching the query
`results`	Yes	List of comment objects
`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 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "docket_id": "EPA-HQ-OAR-2021-0317"
+  },
+  {
+    "document_id": "EPA-HQ-OAR-2021-0317-0001",
+    "posted_from": "2023-06-01",
+    "posted_to": "2023-12-31"
+  }
+]

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 comment objects",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "description": "Comment 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 comments 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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds minimal behavioral context, noting the comments are public and showing an example document ID. It does not explain pagination, result limits, or how filters interact, but the annotations lower the burden.

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?

The description is a single, compact sentence that front-loads the main purpose and includes a helpful example. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 optional parameters and an output schema, the description gives a high-level overview but does not explain how filters combine (e.g., docket_id vs document_id) or provide guidance on result handling. The example is useful, but the interaction between filters is left to schema inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds value by providing a concrete document ID format example and grouping filters into free-text and date categories, which helps clarify parameter usage beyond the schema's individual descriptions.

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?

The description clearly identifies the resource as 'public comments' and indicates the tool filters by docket, document, free-text, or date. It is clear this is a search tool, but it does not explicitly distinguish it from sibling tools like get_comment, so it lacks sibling differentiation.

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

Usage Guidelines3/5

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

The description implies usage by listing filter criteria and providing an example, but it does not explicitly state when to use this tool over alternatives or mention exclusions. The guidance is implied rather than directly stated.

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.