Skip to main content
Glama

Regulations Gov

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Comment

get_comment
Read-onlyIdempotent

Single public comment by comment ID. Returns text, submitter, posting date, attachments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesComment ID
include_attachmentsNoInclude attachment list (default true)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoComment ID
typeNoResource type
includedNoIncluded attachment resources

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "comment_id": "EPA-HQ-OAR-2021-0317-0042"
+  },
+  {
+    "comment_id": "FDA-2023-D-1234-5678",
+    "include_attachments": true
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "id": {
+      "description": "Comment ID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "included": {
+      "description": "Included attachment resources",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "description": "Attachment ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Resource type",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "description": "Resource type",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context by noting the comment is 'public' and lists the returned fields (text, submitter, posting date, attachments), which goes beyond 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?

The description is two sentences with no filler. The first sentence states the core purpose immediately, and the second succinctly lists the return contents, making it highly efficient and well-structured.

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

Completeness5/5

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

Given the low complexity, rich annotations, full schema coverage, and presence of an output schema, the two-sentence description is complete. It conveys the essential usage (by comment ID) and expected return fields without needing further elaboration.

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%, with both comment_id and include_attachments having descriptions in the schema. The tool description does not add new parameter-specific semantic detail beyond confirming ID-based lookup, so the baseline of 3 is appropriate.

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 opens with 'Single public comment by comment ID', clearly stating the verb (retrieve) and resource (a comment) with a specific selector. This distinguishes it from sibling tools like search_comments, which handle broader search, making the purpose unambiguous.

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 phrase 'Single public comment by comment ID' clearly implies that this tool should be used when the agent has a known comment ID and needs one specific comment. It does not explicitly mention alternatives or exclusions, but the context is sufficiently clear for selection.

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

All Regulations Gov toolsInspect
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.

Resources