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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

State Session Law Versions

get_session_law_versions
Read-only

List every version of a state session law with timestamps, hashes and current-version status, so you can see when text changed. Use the version with get_session_law_body to read it.

Instructions

Every version of one STATE session law that we served or adopted, newest first, and which is current. A law's text can be corrected after it is first served, so the version read yesterday may not be the one a plain body call returns today. Lists when each was recorded, its length, hash and how the text was taken; carries no text. Read one version with get_session_law_body and its version. Takes an id, not a citation. Charged once per call; a law with a single version still answers.

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": {
      "session_law_id": "<session_law_id>"
    },
    "name": "get_session_law_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_law_idYesA state session law id, e.g. `SSL_MN_2025S1_G_Y2025_C1`, from list_session_laws or get_session_law. Pass the id, not a citation: resolve a citation with get_session_law first. Federal `SAL_` ids 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
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavior: newest-first ordering, a current-version marker, the caveat that post-service corrections mean yesterday's version may differ from what a plain body call returns, and that metadata (recorded time, length, hash, extraction method) is returned but not text. The billing note ("Charged once per call; a law with a single version still answers") answers the no-results edge case. It stops short of describing pagination or version-count bounds.

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 what is returned and in what order, then routing to the body tool, then prerequisites and cost. Dense and largely waste-free, though the id-not-citation point duplicates the schema and the billing sentence sits slightly awkwardly at the end.

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?

Given an output schema exists, the description still usefully signals that metadata rather than text is returned, which is the key expectation to set. For a two-parameter read tool with full annotations, nothing an agent needs in order to call 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 coverage is 100% and both parameters carry full descriptions, so the schema does the heavy lifting. The description's "Takes an id, not a citation" restates the schema rather than adding syntax or format meaning, so 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 verb and resource: every version of one STATE session law, newest first, with the current one flagged. It also draws the boundary against the sibling that returns text ("carries no text. Read one version with get_session_law_body"), so an agent can choose 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 Guidelines5/5

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

Names the alternative explicitly and the condition that selects it: use get_session_law_body with a `version` when the text itself is needed. It also states the id-vs-citation prerequisite ("Takes an id, not a citation"), which is the most common failure mode for this family.

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