Skip to main content
Glama
Sign In
regintel-mcp

regintel-mcp

by Black-Swan-Causal-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_comment

Retrieves a single regulations.gov comment with its body text, submitter details, attachment metadata, and extracted attachment text; use max_chars to limit long content.

Instructions

One comment in full: body text, submitter fields (organization, name, category, location), attachment metadata and extracted attachment text. max_chars truncates long texts.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNo
max_charsNo
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 carries the full burden. It does disclose the return payload shape and the truncation behavior of max_chars, which is genuinely useful, but it says nothing about the 'refresh' parameter's effect (cache bypass?), permission requirements, or what happens when a comment_id is missing.

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?

A single dense sentence that front-loads the resource and then lists the returned fields, with the truncation caveat appended. No filler, though the colon-and-list construction is slightly compressed at the cost of readability.

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?

There is no output schema, so the description must describe return values, and it does so adequately. However, for a three-parameter tool with zero schema coverage, the unexplained 'refresh' flag and the absence of any error or permission context leave a meaningful gap.

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 explains max_chars ('truncates long texts') and comment_id is self-evident, but 'refresh' is left completely unexplained despite being a non-obvious behavioral toggle. One of three parameters is undocumented in both schema and description.

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 names a specific resource ('One comment in full') and enumerates exactly what is returned: body text, submitter fields, attachment metadata and extracted attachment text. That is enough to distinguish it from list_comments, though it never explicitly states the retrieval verb or names the sibling.

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?

Usage is only implied: 'One comment in full' suggests fetching a single record versus the sibling list_comments, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the routing decision from the phrase 'in full'.

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

Deploy Server

Other Tools