Skip to main content
Glama

get_regulatory_comment_deadlines

Read-only

Use when tracking Federal Register proposed rules and notices with open comment periods. Filters comment windows client-side on comments_close_on when API cannot server-side filter. Source: Federal Register API. $0.10 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_regulatory_comment_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNo
agenciesNo
days_aheadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses a real behavioral quirk: comment windows are filtered client-side on comments_close_on when the API cannot server-side filter, which warns the agent about possible over-fetching. It also states the upstream source and a per-call cost of $0.10 USDC, useful for budgeting decisions. It does not describe result volume, pagination, or ordering.

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 tight sentences with the usage trigger front-loaded, followed by the filtering caveat and provenance/cost. Every sentence carries information, though the 'Source:' fragment is terse enough to read as a metadata tag rather than prose.

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?

For a read-only, open-world query tool with no output schema and no parameter documentation, the description covers purpose, source, cost, and filtering behavior but says nothing about what a result contains (fields, per-rule comment counts, deadline format) or how to size days_ahead. Adequate to select the tool, insufficient to call it confidently.

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% and there are three parameters, so the description carries the burden. It never explains term (search keywords?), agencies (agency name strings, up to 10), or days_ahead (the 1-180 forward window), leaving the most decision-relevant parameter undocumented. The comments_close_on reference hints at date filtering but does not map to any named parameter.

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 concrete resource and scope: Federal Register proposed rules and notices with open comment periods, i.e. comment deadlines. The verb is implicit ('tracking') rather than stated, and no sibling is named as a contrast, so differentiation from tools like get_regulatory_news_synthesis is left to inference.

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?

It opens with an explicit trigger condition ('Use when tracking Federal Register proposed rules and notices with open comment periods'), which is enough for an agent to decide relevance. It offers no when-not guidance and names no alternative tool for adjacent regulatory needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources