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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

State Session Laws (Batch)

get_session_laws_batch
Read-only

Reads up to 50 US state session laws in one call by ID or citation, returning served records in laws and misses in notFound; optionally includes each law's first page of text.

Instructions

Read up to 50 US state session laws in one call, by sessionLawId or citation: the record get_session_law returns, for each. Every entry is answered: served laws in laws, each carrying the input it answers, and the rest in notFound with a status. Duplicates collapse first. includeBody adds the first page of each law's text at the body price. To identify citations use resolve_statute_citations_batch; use this to read the records.

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": {
      "ids": "<ids>"
    },
    "name": "get_session_laws_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesSession law ids or citations (`Minn. Laws 2025, ch. 1`, `S.F.No. 1552`), at most 50 distinct entries after duplicates collapse (200 raw, 300 characters each). A citation also pays the resolve price. Federal `SAL_` ids are misses and are never charged.
includeBodyNotrue adds the first page (about 30,000 characters) of each served law's text as `body`, at the body price per law served. A withheld or not-held law gets body: null and is not charged for it. Continue a long act with get_session_law_body from bodyNextCursor.
jurisdictionNoOptional two-letter state code, `dc` or `pr`, applied to every citation in ids: it supplies a state a citation omits and rejects one that conflicts. Ignored for ids. `federal` or an unknown code is a 422, nothing charged.
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.2/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, so the safety profile is covered; the description adds genuinely new behavior: every entry is answered (served in `laws` with its originating `input`, the rest in `notFound` with a status), duplicates collapse before counting, and includeBody is billed 'at the body price'. Pricing and partial-failure semantics are exactly the kind of context annotations cannot carry.

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-loads the verb, resource, and batch limit, then moves to response shape, dedup, and pricing. Dense but nearly every clause carries information; the includeBody pricing clause partially restates the schema description, which is the only real redundancy.

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 values needn't be spelled out, yet the description still gives the envelope (laws/notFound) an agent needs to interpret partial results. Combined with the dedup rule, the body-pricing note, and the citation-resolution pointer, nothing material is missing for a batch read tool.

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%, so the schema already documents all four parameters in detail, including the 50-distinct/200-raw limit and the jurisdiction conflict rule. The description only echoes the ids/citation duality and the includeBody first-page behavior, adding little beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 ('Read up to 50 US state session laws in one call'), the accepted identifiers (sessionLawId or citation), and explicitly equates the result to 'the record get_session_law returns', which cleanly separates it from the single-record sibling. It also names resolve_statute_citations_batch as the different job, so an agent can route 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 an explicit routing rule: use resolve_statute_citations_batch to identify citations, 'use this to read the records'. It also implies batching is preferred over repeated get_session_law calls by framing itself as the batch equivalent. It does not explicitly state when a single get_session_law call is preferable, which keeps it short of a 5.

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