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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Regulations.gov Docket

get_rulemaking_docket
Read-only

Retrieve a Regulations.gov docket's agency, title, abstract, RIN, document counts, and comment count by docket ID. Use it to check current rulemaking status before listing documents.

Instructions

One Regulations.gov docket, rulemaking or non-rulemaking: agency, type, title, abstract, the RIN when the agency entered one, when it was last modified, how many documents we hold and of which types, and the comment count when we measured it (null means not measured, never zero). Current state only; no comment text. Takes a docket_id such as EPA-HQ-OAR-2021-0208. An unknown docket is a 404 and is refunded. Read the documents with list_docket_documents.

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

Input Schema

NameRequiredDescriptionDefault
docket_idYesRegulations.gov docket id, for example `EPA-HQ-OAR-2021-0208`. Case is kept as printed.
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?

Goes well beyond the readOnly/destructive annotations by disclosing billing behavior on failure ('An unknown docket is a 404 and is refunded'), the measurement semantics of the comment count ('null means not measured, never zero'), and the scope limit that it returns current state with no comment text. These are exactly the operational details an agent cannot infer from structured fields.

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-loaded with identity and field coverage, then routing and failure semantics, with no filler sentences. The middle field enumeration is dense and slightly list-like, but each item conveys a real attribute of the response rather than padding.

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 no prose, yet the description still adds the pieces the schema cannot: failure behavior and refund, null-vs-zero measurement semantics, current-state-only scope, and the correct sibling for document bodies. Nothing an agent needs 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 coverage is 100%, so both docket_id and Idempotency-Key are already fully documented, including the id pattern, length limits, and retry/replay semantics. The description only restates the id with the same example the schema gives and says nothing about the idempotency key. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

Opens with a specific verb+resource ('One Regulations.gov docket, rulemaking or non-rulemaking') and enumerates exactly what is returned: agency, type, title, abstract, RIN, last-modified, document counts by type, and comment count. The singular scope plus the example id makes it clearly distinct from list_rulemaking_dockets, and it names list_docket_documents for the related data.

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 the agent: 'Read the documents with list_docket_documents' tells it when to move to a sibling instead of calling this again. It also sets expectations that this is current-state-only metadata with no comment text. It does not explicitly contrast with list_rulemaking_dockets, but the singular framing implies the distinction.

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