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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Unified Agenda History of a RIN

list_rin_agenda
Read-only

Retrieve the Unified Agenda history for one RIN, one entry per edition from Fall 1995 onward, newest first, with each edition's stage, priority and timetable. Filter by edition range using from and to.

Instructions

The Unified Agenda history of one RIN: one entry per edition that carried it (Fall 1995 onward), newest first, each with the stage, priority and timetable the agency printed in that edition. Narrow with from and to (edition ids YYYYMM, such as 202510). Charged per page; a RIN no edition carries is a 404 and is refunded. Use get_rulemaking_rin for the linked dockets and Federal Register documents.

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": "list_rin_agenda"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoNewest Unified Agenda edition to include, as an edition id `YYYYMM`, for example `202510`. Must not be earlier than `from`.
rinYesRegulation Identifier Number `NNNN-XXNN`; lower case is accepted.
fromNoOldest Unified Agenda edition to include, as an edition id `YYYYMM`, for example `202010`. Must not be later than `to`.
limitNoEditions per page, 1 to 100. Default 25.
cursorNo`nextCursor` of the previous page; same filters.
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.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing the billing model (charged per page), the failure semantics (a RIN no edition carries is a 404 and is refunded), and the ordering of results. Those are exactly the operational facts an agent needs before spending credits on a call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences: grain and contents first, then filtering, then cost/failure behavior, then the sibling hand-off. Nothing is redundant and the most decision-relevant facts are front-loaded.

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 paginated, metered read tool with a 6-parameter schema and an output schema, the description covers grain, ordering, filtering, pagination cost, and error/refund behavior. Return-value structure is already carried by the output schema, so nothing material 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 schema already documents the YYYYMM edition-id format, the from/to ordering constraint, and the cursor. The description's 'Narrow with from and to (edition ids YYYYMM, such as 202510)' repeats the schema rather than adding format or interaction detail, so the 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?

States a specific resource (the Unified Agenda history of one RIN), a concrete grain (one entry per edition that carried it, Fall 1995 onward), an ordering (newest first) and the fields each entry contains. An agent can tell this apart from get_rulemaking_rin, which is explicitly named for the docket/FR-document view.

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?

Gives explicit routing: use this tool for per-edition agenda history, and use get_rulemaking_rin for linked dockets and Federal Register documents. It also tells the agent to narrow with from/to, so the correct invocation pattern is unambiguous.

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