va-lis-mcp

get_communication

One communication between the chambers: each statement and the bills it names.

Instructions

One communication between the chambers: each statement and the bills it names.

statements are the clerk's sentences in order ("THE SENATE HAS PASSED THE FOLLOWING HOUSE BILLS:"), each with its bills, their chief patrons, and the document_code of the text version acted on. A communication records what a chamber did, not how it voted: it carries no vote ids. LIS holds structured content from May 2024 on. An older communication comes back with no statements and an html link to the original.

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": {
      "communication_id": "<communication_id>"
    },
    "name": "get_communication"
  }
}

Input Schema

Name	Required	Description	Default
`communication_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Oct 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains the return shape (statements, bills, chief patrons, document_code), states explicitly that it carries no vote ids, and discloses the May 2024 LIS data cutoff plus the fallback html link for older records. It omits auth or pagination behavior, so not a 5.

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 the core statement ('One communication between the chambers'), followed by structured disclosure of return contents and data limits. Every sentence earns its place, though the domain framing is slightly verbose.

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, the description usefully describes what comes back and the data-availability caveat, which is what an agent needs to interpret results. The only real gap is how to source the communication_id, a minor omission for a single-parameter lookup.

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?

The single communication_id parameter has 0% schema description coverage, and the description adds no format, sourcing, or validity guidance for it. The field name is largely self-explanatory, so this lands at the minimum-viable baseline rather than being penalized further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieves 'one communication between the chambers,' and immediately scopes it as the statements plus the bills they name. This clearly separates it from list_communications, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the singular retrieval framing and the sibling list_communications, but the description never states when to reach for this tool versus listing or other bill tools, nor any prerequisites for obtaining a valid id.

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