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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Rules Committee Records

list_rulemaking_committee_records
Read-only

Retrieve Judicial Conference Rules Committee drafting records—minutes, reports, rules packages, comments—newest first, filtered by committee, document type, year, rule set, rule, or docket.

Instructions

List Judicial Conference Rules Committee records (minutes, agenda books, reports, rules packages, comments), newest first. Filter by committee, docType, year, ruleSet, rule (needs ruleSet) and docketId. Drafting history, not law. Public comments and suggestions (textWithheld: true) withhold title, filename, sourceUrl, itemUrl and text: they name private people. Charged per page; an empty page is refunded. Read one with get_rulemaking_committee_record.

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

Input Schema

NameRequiredDescriptionDefault
ruleNoRule number, for example `26`; needs `ruleSet`.
yearNoYear of the record, for example `2024`.
limitNoPage size, 1 to 100.
cursorNo`nextCursor` of the previous page; same filters.
docTypeNoOne of: meeting_minutes, agenda_books, committee_reports, rules_packages, preliminary_drafts, superseded_pamphlets, rules_comments, rules_suggestions, fjc_studies, past_members, special_projects, style_resources, transcripts_testimony, rules_comments_archive.
ruleSetNoFRCP, FRAP, FRBP, FRCRP or FRE: records that discuss a rule of this set.
docketIdNoOnly records linked to this rulemaking docket id, for example `USC-RULES-CV-2025-0004`.
committeeNoThe Judicial Conference committee that produced the record: Standing, Appellate, Bankruptcy, Civil, Criminal, Evidence or General.
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.2/5.0
Behavior4/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing newest-first ordering, per-page charging with an empty-page refund, and a detailed redaction rule for public comments and suggestions (title, filename, sourceUrl, itemUrl and text withheld because they name private people). The only omission is pagination mechanics, which the cursor parameter already conveys.

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-loads the verb, resource and ordering, then packs filters, scope caveat, redaction rule and the single-record pointer into compact sentences with no filler. The redaction sentence is dense but each clause carries non-obvious information.

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?

For a 9-parameter read-only list tool with an output schema, the description covers ordering, filtering, cross-parameter constraints, cost behavior and the textWithheld output caveat. Nothing an agent needs to call it correctly or interpret the response safely 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%, so every parameter including the enum-like docType and ruleSet lists is already documented, and the ruleSet dependency appears in the schema itself. The description's filter enumeration mostly restates what the schema provides, adding little syntax or format detail; 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?

Opens with a specific verb and resource ("List Judicial Conference Rules Committee records") and enumerates the content types (minutes, agenda books, reports, rules packages, comments) while naming get_rulemaking_committee_record as the single-record counterpart. An agent can distinguish this from the sibling get_ tool and the docket/statute listers without opening any 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?

Gives concrete filter guidance (committee, docType, year, ruleSet, rule, docketId), states the dependency "rule (needs ruleSet)", and routes single-record reads to get_rulemaking_committee_record. It also frames scope with "Drafting history, not law", which implicitly steers statute-related queries elsewhere, though no sibling is named as an explicit alternative for that case.

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