Skip to main content
Glama
Vaquill-AI/vaquill-mcp

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Regulations.gov Dockets

list_rulemaking_dockets
Read-only

List and filter Regulations.gov dockets by agency, docket type, RIN, and modified-date window, returned most recently modified first, to locate relevant rulemaking activity.

Instructions

List and filter Regulations.gov dockets, most recently modified first, by agencyId, docketType (Rulemaking or Nonrulemaking), rin, hasRin and a modifiedSince/modifiedUntil window. Charged per page; an empty page is still charged. nextCursor is bound to the filters that produced it, so pass it back with the same filters. Read one with get_rulemaking_docket.

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

Input Schema

NameRequiredDescriptionDefault
rinNoRegulation Identifier Number `NNNN-XXNN`; lower case is accepted.
limitNoPage size, 1 to 100.
cursorNo`nextCursor` of the previous page; same filters.
hasRinNo`true` keeps only dockets that carry a RIN, `false` only those without one.
agencyIdNoOnly dockets of this agency, by Regulations.gov agency acronym. Case is ignored.
docketTypeNoOnly dockets of this type: `Rulemaking` or `Nonrulemaking`.
modifiedSinceNoOnly dockets modified at or after this ISO-8601 instant.
modifiedUntilNoOnly dockets modified before this ISO-8601 instant (exclusive). The window is half-open, `modifiedSince` <= modified < `modifiedUntil`, so equal bounds select nothing and are refused with a 422: `modifiedUntil` must be after `modifiedSince`.
Idempotency-KeyNoOptional, 16 to 255 visible ASCII characters (a UUIDv4 is ideal). A retry with the same key and request replays the original 2xx for 24 hours without charging again; the same key with a different request is rejected.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), yet the description adds genuinely new behavior: per-page billing including charged empty pages, and the constraint that nextCursor is bound to the filters that produced it. The sort order is also disclosed, which is behavioral information no structured field provides.

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 sentences, front-loaded with purpose, then cost, then cursor constraint, then the sibling pointer — no filler. The enumerated filter list partially duplicates the schema and could be trimmed, which keeps it off a 5.

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?

An output schema exists so return values need not be explained; an agent gets purpose, filter axes, ordering, cost model, and cursor-replay constraints. Nothing needed to call this correctly is missing.

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 description coverage is 100% and the schema is unusually rich (pattern, examples, the half-open window rule, Idempotency-Key replay semantics). The description largely restates the filter names and the docketType values already encoded in the schema, adding little syntax or format meaning beyond it, so the baseline 3 applies.

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?

States a specific verb and resource ('List and filter Regulations.gov dockets'), the sort order ('most recently modified first'), and the exact filter axes (agencyId, docketType, rin, hasRin, modifiedSince/modifiedUntil). It also names the sibling that reads a single docket, so an agent can distinguish list vs. get without opening either schema.

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?

Explicitly routes single-record retrieval elsewhere ('Read one with get_rulemaking_docket') and implies use for filtered enumeration. It does not state any when-not-to-use case beyond that routing (e.g., prefer a count or another list tool for non-rulemaking corpora), so it falls just short of full guidance.

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