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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Documents in a Docket

list_docket_documents
Read-only

List a Regulations.gov docket's documents, oldest first, returning metadata only and filtering by document type, open-for-comment status, and posted date range.

Instructions

The documents of one Regulations.gov docket, oldest first: the proposal, notices, final rule and supporting material, with comment periods and Federal Register document numbers. Metadata only, no document text and no comments. Filter by documentType, openForComment and a postedFrom/postedTo window. Charged per page; an unknown docket is a 404 and is refunded.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 1 to 100.
cursorNo`nextCursor` of the previous page; same filters.
postedToNoOnly documents posted before this ISO-8601 instant (exclusive). The window is half-open, `postedFrom` <= posted < `postedTo`, so equal bounds select nothing and are refused with a 422: `postedTo` must be after `postedFrom`.
docket_idYesRegulations.gov docket id, for example `EPA-HQ-OAR-2021-0208`. Case is kept as printed.
postedFromNoOnly documents posted at or after this ISO-8601 instant.
documentTypeNoOnly documents of this Regulations.gov document type. Case is ignored.
openForCommentNo`true` keeps only documents whose comment period is open.
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.3/5.0
Behavior5/5

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

Annotations only cover read-only/non-destructive/open-world; the description adds substantive behavior beyond that: ordering, per-page charging, and that an unknown docket returns a 404 that is refunded. Cost and error-refund semantics are exactly the operational facts annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with what the tool returns, then exclusions, then filters, then billing/error semantics. No filler and nothing repeated from the schema's own wording.

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?

Strong on scope, cost and error behavior, and an output schema covers return values. However, with 8 parameters and stateful paging via cursor plus idempotent retries, the description never mentions pagination or retry behavior, leaving the agent to discover paging semantics from the schema alone.

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%, so the schema already documents limit, cursor, docket_id, the half-open posted window, and the Idempotency-Key replay rules. The description only restates which filters exist and adds no syntax or edge-case detail beyond them; 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 ("The documents of one Regulations.gov docket") plus ordering ("oldest first") and the concrete contents (proposal, notices, final rule, supporting material, comment periods, FR document numbers). An agent can distinguish this from a docket-metadata or comment tool without opening the 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 bounds scope: "Metadata only, no document text and no comments" tells the agent when this tool is the wrong choice, and the named filters (documentType, openForComment, postedFrom/postedTo) show what narrowing is available. It does not name a specific sibling to use for text or comments, which keeps it from a 5.

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