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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Rulemaking Coverage

get_rulemaking_coverage
Read-only

Check rulemaking store coverage per source, including row counts, newest change, refresh freshness, Unified Agenda editions, and known gaps before treating a missing docket or RIN as absent.

Instructions

What the rulemaking store holds, per source: row counts, newest change, last successful refresh and a freshness verdict (ok, stale or unmeasured), the Unified Agenda editions held, and what is not included and why. Read it before treating a missing docket or RIN as absent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_rulemaking_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds real behavioral context beyond that: it discloses the freshness verdict vocabulary (ok, stale, unmeasured), the fact that exclusions are documented with reasons, and that the store may be incomplete — 'unmeasured' in particular warns that freshness is not always known. It omits cadence/refresh mechanics and any size or rate considerations.

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?

It is a single sentence plus a short imperative, with the payoff instruction ('read it before treating a missing docket as absent') placed at the end where it lands. The middle enumeration is dense and run-on, slightly reducing scannability, but every listed item corresponds to real output content.

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?

With an output schema present, the description need not explain return structure, yet it still summarizes the returned dimensions and, crucially, warns about incompleteness and why items are excluded. For a zero-param coverage tool, an agent has everything needed to decide to call it and how to interpret a null result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4 and there is no parameter meaning for the description to convey. Nothing in the input schema needs compensating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and its scope: it reports what the rulemaking store holds per source, itemizing row counts, newest change, last refresh, freshness verdict, Unified Agenda editions, and exclusions. An agent can tell this is a metadata/coverage report rather than a docket or RIN fetch, which separates it from siblings like get_rulemaking_docket or get_rulemaking_rin. It stops short of naming a sibling coverage tool (e.g., list_statutes_coverage) for contrast, so it is just under a 5.

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 an explicit, actionable trigger: 'Read it before treating a missing docket or RIN as absent,' which ties usage to a concrete failure mode an agent will hit. It does not state when not to call it or name an alternative, but for a zero-parameter meta tool the context is clear.

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