regintel-mcp

Overview Schema Source Related Servers Discussions Admin

list_comments

Retrieves all public comments in a docket with pagination handled, returning comment IDs, titles, dates, submitters, and flags for attachments, stubs, and duplicates so you can review public input.

Instructions

All public comments in a docket (pagination handled). Each row: commentId, title, postedDate, submitterName, and — once build_corpus has run — has_attachment, is_stub (body < 50 chars and no attachment) and duplicate_of (same submitter, near-identical text). Flags never drop rows.

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": {
      "docket_id": "<docket_id>"
    },
    "name": "list_comments"
  }
}

Input Schema

Name	Required	Description	Default
`refresh`	No
`docket_id`	Yes
`include_withdrawn`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses key behavior: pagination is handled internally, rows are never dropped by flags, and some fields only appear after build_corpus has run. But it does not state privacy/withdrawn filtering behavior (does include_withdrawn default false exclude withdrawn comments?) or the returned row type guarantees.

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?

Front-loads the scope in the first clause and then enumerates returned fields compactly. The parenthetical and dash-clauses are dense but each carries information; minor awkwardness in the long final sentence.

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?

No output schema and no annotations, so the description must stand alone for a 3-parameter list tool. It covers return fields and flag semantics partially, but omits how include_withdrawn and refresh alter results and what happens when build_corpus hasn't run.

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

Parameters2/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 compensate. It mentions docket scope and implicit pagination but never explains refresh, include_withdrawn, or their defaults/effects, leaving two of three parameters undocumented.

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 (list) and resource (public comments in a docket), and distinguishes itself from get_comment by being a collection lister. It doesn't explicitly contrast with sibling tools like list_documents, but the scope is clear enough for an agent to choose it.

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 use when you need a docket's comments and notes that pagination is handled, which is useful context. However, it gives no explicit when-to-use vs get_comment or condition for the refresh/include_withdrawn flags, leaving selection partly inferred.

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

Deploy Server