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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Federal Register Documents for a CFR Part

get_part_rulemaking
Read-only

Retrieve Federal Register rules, proposed rules, and notices tied to a specific CFR title and part, newest first, over a bounded window of recent publication years.

Instructions

Every Federal Register rule, proposed rule and notice whose CFR references include one title and part, newest first. The window is bounded to the years most recent publication years (default 5, max 12), and coverage says when a year was truncated. Use get_section_rulemaking for one section, and get_rulemaking_rin for the whole rulemaking behind a RIN.

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": {
      "title": "<title>",
      "part": "<part>"
    },
    "name": "get_part_rulemaking"
  }
}

Input Schema

NameRequiredDescriptionDefault
partYesCFR part number, e.g. `314`.
titleYesCFR title number (1 to 50).
yearsNoHow many CALENDAR years of Federal Register publications to read: the current calendar year and the `years - 1` before it. It is not a trailing window of 365-day periods, so early in a year `years=1` covers only the days elapsed so far. The years read are echoed in `years`.
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
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds behavior the annotations cannot: newest-first ordering and a bounded year window with a `coverage` signal for truncated years. It stops short of covering pagination/result-count limits, which is the only remaining behavioral gap given an output schema exists.

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 the resource and ordering, then the window constraint, then sibling routing. No filler, though the window clause partially duplicates what the schema already says about `years`.

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?

Returns are covered by the output schema, safety and openness by annotations, and parameters by a fully described schema; the description supplies the remaining pieces (ordering, window bounding, sibling disambiguation). Nothing an agent needs in order 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 `years` parameter is already documented in detail (calendar-year semantics, not a trailing 365-day window, echoed in the response), so the description largely restates it. It adds only a weak link between `years` and the `coverage` truncation signal, which is already implied. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Names a specific resource ("Every Federal Register rule, proposed rule and notice") and scopes it precisely to documents whose CFR references include one title and part, plus an ordering guarantee ("newest first"). The final sentence explicitly distinguishes it from get_section_rulemaking and get_rulemaking_rin, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing sentence names both alternatives and the exact condition that selects each: section-level lookups go to get_section_rulemaking, whole-rulemaking-by-RIN goes to get_rulemaking_rin. That is explicit when-to-use-this-vs-sibling guidance, not implied.

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