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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Rulemaking by RIN

get_rulemaking_rin
Read-only

Retrieves all held regulatory records for one RIN, including Unified Agenda entries, OIRA reviews, dockets, Federal Register documents, CFR parts, related laws, and coverage gaps.

Instructions

Everything we hold for one Regulation Identifier Number (NNNN-AANN, such as 2060-AV16): the latest Unified Agenda entry, OIRA reviews, Regulations.gov dockets, Federal Register documents by role (proposed, final, correction), CFR parts, public laws and related RINs, each link with its basis and quality. An ambiguous link carries no pick. coverage lists what we do not hold. An unknown RIN is a 404 and is refunded. For edition history use list_rin_agenda.

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": {
      "rin": "<rin>"
    },
    "name": "get_rulemaking_rin"
  }
}

Input Schema

NameRequiredDescriptionDefault
rinYesRegulation Identifier Number `NNNN-XXNN`; lower case is accepted.
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?

Annotations only declare it as a safe, non-open-world read. The description adds real behavior the agent could not otherwise know: each link carries a basis and quality signal, ambiguous links are deliberately left unpicked, `coverage` reports what is NOT held (so absence is not silently a gap), and an unknown RIN returns 404 and is refunded. The refund/charge semantics are operationally important and appear nowhere in the structured fields.

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-loaded with the resource and its scope, then the enumeration, then the caveats (coverage, 404/refund, sibling routing). Dense but nearly every clause carries information; the parenthetical format example is slightly redundant with the schema.

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?

An output schema exists, so return-value shape need not be described, and the description still covers the things the schema cannot: missing-data disclosure via `coverage`, link-quality semantics, 404 behavior, and billing on a miss. For an aggregation tool of this complexity, nothing an agent needs to invoke it 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 both parameters (rin pattern/example, Idempotency-Key replay semantics) are fully documented in the schema itself. The description's RIN format note (NNNN-AANN, 2060-AV16) restates the schema, and it says nothing about the idempotency key. Baseline 3 is appropriate.

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 the exact resource (one RIN) and enumerates what the response aggregates: Unified Agenda entry, OIRA reviews, Regulations.gov dockets, Federal Register documents by role, CFR parts, public laws and related RINs. It also explicitly differentiates from the sibling list_rin_agenda by assigning edition history there, so an agent can pick between the two 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 Guidelines4/5

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

Gives a clear routing rule: this tool for everything on one RIN, list_rin_agenda for edition history. It does not spell out when-not conditions beyond that (e.g. bulk lookups across many RINs), but the single-RIN scope is unambiguous from the opening phrase.

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