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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Federal Register Documents for a CFR Section

get_section_rulemaking
Read-only

Retrieve Federal Register documents tied to a CFR section using its source note and eCFR amendment dates, with match quality, staleness, and coverage signals for reliable rulemaking leads.

Instructions

The Federal Register documents behind one CFR section, from the section's printed source note and from eCFR amendment dates. matchBasis says which signal matched and quality is verified only when both agree; a candidate is a lead, not a finding. noteIsStale means eCFR records an amendment newer than the note prints. Read coverage before treating a missing document as absent. A document with one valid RIN carries rulemakingUrl, a pointer to get_rulemaking_rin. CFR sections only.

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": {
      "act_id": "<act_id>"
    },
    "name": "get_section_rulemaking"
  }
}

Input Schema

NameRequiredDescriptionDefault
act_idYesSection identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable from a citation but the CHAPTER is not, so hand-built ids usually 404.
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?

The description adds substantial behavior beyond the annotations: matchBasis explains which signal matched, quality is verified only when both signals agree, candidate is only a lead, noteIsStale flags newer eCFR amendments, and coverage must be checked before concluding a document is absent. It also explains rulemakingUrl and its relationship to get_rulemaking_rin. Nothing here contradicts readOnlyHint, openWorldHint, or destructiveHint.

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 dense but front-loads the core purpose and keeps every sentence relevant to interpretation. The important scope restriction 'CFR sections only' is placed at the very end, which slightly weakens structure. Overall it is compact and avoids filler.

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 two-parameter read-only tool with an output schema, the description is complete enough to call correctly. It explains the key output-quality signals, coverage caveat, stale-note condition, and sibling handoff without needing to document return structure already covered by the output schema.

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 input schema already fully documents act_id and Idempotency-Key, including the warning against hand-assembling section ids. The description adds only the domain constraint that inputs must be CFR sections, not USC sections. That is useful but minimal beyond what the schema provides.

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 resource: the Federal Register documents behind one CFR section, drawn from the source note and eCFR amendment dates. It also scopes the tool with 'CFR sections only' and distinguishes its RIN pointer from get_rulemaking_rin, so an agent can identify it apart from statute-oriented siblings.

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 gives a clear domain restriction ('CFR sections only') and routes RIN follow-up to get_rulemaking_rin. It also warns the agent to read coverage before treating a missing document as absent. It does not explicitly compare against other section-level siblings such as get_section_changes or get_part_rulemaking, so it falls short of full when-to-use guidance.

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