Skip to main content
Glama
va-lis-mcp

va-lis-mcp

by JonnyWaffles

get_minutes_book

One minutes book: each action a chamber or committee took that day, in order.

Instructions

One minutes book: each action a chamber or committee took that day, in order.

One record per action, with the bill, the section of business it fell under, the action taken, and the tally. A vote_id here belongs to the bill beside it, which a vote_id in get_bill_history does not always do: pass it with the bill number and the session code to get_roll_call. The tally keeps a presiding officer's tiebreak ("18-Y 18-N 0-A, Chair votes Yea"), which the vote record drops. is_block marks one motion that disposed of many bills, and is_voice a vote that names no members. include_procedural adds the entries that name no bill: the call to order, recesses, communications received. A floor day runs to about 200 records; limit is capped at 200, page with offset.

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": {
      "minutes_book_id": "<minutes_book_id>"
    },
    "name": "get_minutes_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
minutes_book_idYes
include_proceduralNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations, so the description carries the full burden and does so richly: ~200 records per floor day, limit capped at 200 requiring offset pagination, is_block meaning one motion disposed of many bills, is_voice meaning no named members, and the tally preserving a chair tiebreak the vote record drops. These are exactly the quirks an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the definition, then layered detail on record shape, vote_id routing, field quirks, filtering, and pagination. Dense but every sentence earns its place; no filler.

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

Completeness4/5

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

With no output schema and zero schema description coverage, the description supplies field semantics, return granularity, and pagination caps, so an agent can call it correctly. The missing piece is how to acquire the required minutes_book_id.

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 0%, so the description must compensate, and it defines limit (capped at 200), offset (pagination), and include_procedural (adds entries naming no bill). The required minutes_book_id is left unexplained, presumably obtained elsewhere, which is the one gap.

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+resource and scope: one minutes book listing every action a chamber or committee took that day, in order. It explicitly contrasts its vote_id semantics with get_bill_history and routes to get_roll_call, so an agent can tell it apart from sibling vote tools 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?

Clearly implies the context (day's action log) and names the alternatives get_bill_history and get_roll_call with the condition for using them. It explains include_procedural's effect, but never states the prerequisite of obtaining minutes_book_id from list_minutes_books, nor when-not to use it.

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