va-lis-mcp

get_session

One session with its milestone dates: prefiling, convening, adjournment.

Instructions

One session with its milestone dates: prefiling, convening, adjournment.

events are the dates LIS records for the session, oldest first: "Prefile Date", "Session Start", "Adjournment" (the regular session's sine die), and "Reconvene" (the one day session that takes up the Governor's vetoes and recommendations). projected_date is the planned date LIS holds for an event.

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_code": "<session_code>"
    },
    "name": "get_session"
  }
}

Input Schema

Name	Required	Description	Default
`session_code`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Oct 13, 2026

TDQS

C2.8/5.0

Behavior3/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 disclose useful semantics: events are ordered oldest-first and the named milestone labels are explained, plus what projected_date means. However it says nothing about read-only nature, auth requirements, or result shape beyond those field meanings, so it only partially covers behavior.

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

Conciseness3/5

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

The purpose is front-loaded, but the bulk of the prose is devoted to explaining return-value fields that an output schema already documents, while the callable input goes unexplained. It reads as informational rather than operational, with wasted allocation.

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 event/projected_date explanations are largely redundant, yet they occupy almost the entire description. Missing is the information an agent actually needs to invoke it: the meaning and source of session_code and how this differs from the sibling session tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required session_code parameter, and the description never explains what a session code is or its format. Since the schema does not compensate, the description should have, making this a real gap.

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?

The description leads with 'One session with its milestone dates: prefiling, convening, adjournment,' giving a clear verb (retrieve) and resource (a single session) with topical scope. It is distinguishable from list_sessions and get_current_session via the singular 'One session', though it never names those alternatives explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus get_current_session or list_sessions, and no prerequisites (e.g., where a session_code comes from). The agent must infer from the name alone that this is a single-record lookup by code.

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