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

Vaquill-AI/vaquill-mcp

Official
by Vaquill-AI

Session Laws Affecting a Section

get_section_enactments
Read-only

Find which session laws a publisher's table lists against a code section, including acts that added, amended, or repealed it, effective dates, and a sessionLawId for further reading.

Instructions

The state session laws that a publisher's own 'sections affected' tables list against one code section: which act added, amended or repealed it, the act's effective dates, and a sessionLawId to read with get_session_law. Never a complete amendment history: only acts and sessions we hold. Only some states are supported; any other section answers supported: false and is not charged. Empty with supported: true means no held table lists it.

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": {
      "act_id": "<act_id>"
    },
    "name": "get_section_enactments"
  }
}

Input Schema

NameRequiredDescriptionDefault
act_idYesSection identifier, e.g. `USC_T42_C21_S1983` (Title 42, Chapter 21, Section 1983, written 42 U.S.C. 1983). Take it from a search result rather than assembling it: the title and section are derivable from a citation but the CHAPTER is not, so hand-built ids usually 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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: a coverage caveat ('only acts and sessions we hold'), a state-support limitation, and a billing note that unsupported sections 'are not charged'. Missing: latency, pagination, or result-size expectations.

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?

Dense and front-loaded: the resource and its contents come first, then caveats and edge-case interpretation. Semicolons and clauses are tightly packed but each sentence carries distinct information; only the trailing edge-case sentences feel compressed enough to need a second read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values, and it does cover the key edge cases (unsupported state, empty-but-supported). However, for a read tool returning thin coverage-sensitive data, it says nothing about result size, ordering, or pagination across the session laws returned, leaving the agent to discover operational behavior at call time.

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%, including a detailed act_id warning about hand-built ids 404-ing and the Idempotency-Key replay semantics, so the schema carries the parameter burden. The description adds nothing about act_id or Idempotency-Key, and baseline 3 applies when the schema is this complete.

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 (state session laws for one code section) with its provenance (a publisher's 'sections affected' tables) and enumerates what each result contains: act, effective dates, sessionLawId. It also implicitly distinguishes itself from a full amendment-history sibling by warning 'Never a complete amendment history'.

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 concrete guidance on interpreting results and what to do next ('a sessionLawId to read with get_session_law'), plus how to read the unsupported and empty outcomes. It does not explicitly say when to prefer get_section_changes or another sibling over this tool, so the routing guidance is one-directional rather than complete.

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