Regulations.gov

get_comment_detail

Read-only

Get full details for a single comment.

Returns the comment text field, organization, submitter info (if public),
tracking number, and duplicate comment count. Many comments put their
substance in attachments and the text field only says "See attached";
include_attachments=True returns the attachment download URLs.

Some fields (firstName, lastName, organization) are agency-configurable
and may be hidden. The comment text comes back as plain text (HTML
breaks become newlines; tags and entities are decoded).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "comment_id": "<comment_id>"
    },
    "name": "get_comment_detail"
  }
}

Input Schema

Name	Required	Description	Default
`comment_id`	Yes
`include_attachments`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description still adds meaningful behavior: some fields are agency-configurable and may be hidden, and the text field is normalized (HTML breaks become newlines, tags and entities decoded). It doesn't cover what happens for an invalid or missing comment_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short paragraphs, each a single concern, with the core purpose front-loaded before the attachment caveat and the field-visibility/normalization notes. No filler, though the plain-text decoding note is somewhat peripheral to invocation decisions.

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?

For a two-parameter read tool with an output schema and read-only annotations, the description supplies the missing pieces: return field composition, hidden-field risk, and the attachment gotcha. Only the error/not-found path and the likely source of comment_id are unaddressed.

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 description coverage is 0%, so the description must carry the load for include_attachments, and it does — explaining its default-off implication and what it adds (attachment download URLs) together with the reason to enable it. comment_id is left undescribed, though its meaning is unambiguous from the name and required status.

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?

States a specific verb and resource ('Get full details for a single comment') and immediately enumerates what is returned (text, organization, submitter info, tracking number, duplicate count), so an agent knows this is the detail-fetch counterpart to search_comments. It never names search_comments explicitly, so sibling differentiation is by inference only.

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?

Gives a concrete trigger for the optional parameter: 'Many comments put their substance in attachments and the text field only says "See attached"; include_attachments=True returns the attachment download URLs.' That is real when-to-use guidance. It stops short of stating exclusions or naming which sibling to call first to obtain the comment_id.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.