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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

State Session Law Record

get_session_law
Read-only

Look up a US state session law by ID or citation to get its session, approval and effective dates, affected code sections, official sources, and text status.

Instructions

One US state session law's record: citation, session, approval and effective dates, code sections it affects, official sources and textStatus. v1 covers state acts; federal session laws are on the statute tools. Accepts a sessionLawId or a citation (adds the resolve price, kept even if it does not resolve). A withheld law is still returned, textStatus withheld with withheldReason: we hold its text but a measured defect keeps it from being served.

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

Input Schema

NameRequiredDescriptionDefault
jurisdictionNoOptional two-letter state code, `dc` or `pr`, used only when a citation is sent in place of the id: it supplies a state the citation omits and rejects one that conflicts (a 404, resolve fee kept). Ignored for an id. `federal` or an unknown code is a 422, never charged.
session_law_idYesA state session law id from list_session_laws, e.g. `SSL_MN_2025R_G_Y2025_C1`, or a citation such as `S.F.No. 1552` (resolved, at the extra resolve price). A citation naming several laws is a 404 listing candidates in `didYouMean`. 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.6/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses non-obvious behavior: citation resolution incurs a resolve price that is kept even on failure, a withheld law is still returned with textStatus withheld plus withheldReason, and a conflicting or federal jurisdiction yields a 404/422 with no charge. These are exactly the cost and failure-mode details an agent needs before choosing an input form.

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?

Three dense sentences, front-loaded with the record's contents before the scoping and cost caveats. No filler, though the withheld-law sentence is packed tightly enough that a reader must parse it twice.

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 and full schema descriptions, the description still covers the gaps that matter: state-vs-federal scope, citation resolution cost, and how withheld records surface. Nothing an agent needs to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds decision-relevant meaning: passing a citation instead of an id triggers a billable resolution step whose fee is non-refundable on failure. That consequence shapes parameter choice in a way the schema text only states tersely.

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 names a specific resource (one US state session law record) and enumerates exactly what it contains: citation, session, approval and effective dates, affected code sections, official sources, textStatus. It also scopes itself against the federal case ("federal session laws are on the statute tools"), so an agent can distinguish it from statute siblings 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?

It gives clear usage context: state acts only in v1, federal on statute tools, and the id-or-citation input path. It does not explicitly route the agent among the close siblings (get_session_law_body, get_session_law_changes, get_session_law_versions), so the when-to-use guidance is clear but not exclusionary.

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