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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Rules Committee Record

get_rulemaking_committee_record
Read-only

Retrieves a Rules Committee drafting record by ID, including comment dockets, linked Federal Rules, and paged text for tracing rulemaking history.

Instructions

One Rules Committee record by recordId (rcr_ plus 24 hex): its comment dockets, linked Federal Rules (method, confidence) and a window of page text (pageFrom, pageLimit; nextPage continues). Drafting history, not law. quality needs_ocr: no text yet; quality blank: really empty. Comments and suggestions (textWithheld: true) withhold title, filename, URLs and text. An unknown record is a refunded 404.

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": {
      "record_id": "<record_id>"
    },
    "name": "get_rulemaking_committee_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageFromNoFirst page of the record's text to return, counting from 1. Page through a long record by passing the page after the last one you received.
pageLimitNoPages per call.
record_idYesCommittee record id from the list, `rcr_` and 24 hex characters.
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.1/5.0
Behavior4/5

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

With readOnlyHint, openWorldHint=false, and destructiveHint=false already in annotations, the description adds meaningful behavior: quality=needs_ocr versus blank, textWithheld on comments/suggestions, and that an unknown record is a refunded 404. It does not detail auth or rate limits, but it goes well beyond the annotations.

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?

The description is compact and front-loaded: identity first, then contents, paging, scope caveat, quality states, withholding behavior, and the 404 case. The telegraphic style is dense but each sentence carries operational meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-shape explanation is not required, and the description covers the non-obvious semantic cases an agent needs: OCR-empty records, withheld fields, paging continuation, and refunded 404s. It is essentially complete for a single-record read tool.

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 defines record_id, pageFrom, pageLimit, and Idempotency-Key in detail. The description adds only a little framing around page windows and nextPage continuation; it does not mention Idempotency-Key behavior or add syntax beyond the schema.

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?

The description states a specific verb and resource: fetch one Rules Committee record by recordId, and it enumerates what comes back (comment dockets, linked Federal Rules with method/confidence, and a page-text window). That clearly distinguishes it from the sibling list_rulemaking_committee_records and from other get_* records.

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 signals the lookup flow by saying the recordId comes from the list, explains paging with nextPage, and frames the resource as drafting history rather than law. It does not explicitly name competing tools or state when not to use it, but the context is sufficient for selection.

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