va-lis-mcp

get_member_office

A member's district office: postal address, phone, and email.

Instructions

A member's district office: postal address, phone, and email.

The district office is the contact detail LIS publishes nowhere else; get_member has the Capitol room, phone, and email. The record is not session scoped, so there is no session code. Many members have no record, and found is false for them.

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": {
      "member_id": "<member_id>"
    },
    "name": "get_member_office"
  }
}

Input Schema

Name	Required	Description	Default
`member_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0Oct 13, 2026

TDQS

A4.1/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. It discloses meaningful behavior: the record is not session scoped (no session code), and many members have no record with found=false. It does not explicitly confirm the operation is a read, but for a simple public getter the missing-record and scoping disclosures are the substantive traits.

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 resource and its returned fields, followed by routing and edge-case notes. Every sentence carries information (fields, sibling distinction, session scoping, found flag) with only mild verbosity in the 'publishes nowhere else' phrasing.

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?

An output schema exists, so return shape needn't be explained, and the description still covers the important found=false edge case and session-scoping absence. Complete enough for a single-parameter getter with a documented response.

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 0% and the single parameter member_id has no documentation in either schema or description. The description frames the context as a member but adds nothing about the identifier's origin or format; for an obvious numeric id this is acceptable but not compensating.

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 (get) and resource (member's district office) and enumerates the returned contact fields (postal address, phone, email). It explicitly distinguishes itself from the get_member sibling by noting the Capitol room belongs there, so an agent can separate the two without opening either 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?

It names the alternative (get_member) and the distinguishing condition (Capitol room vs district office), which routes the agent correctly. It also warns that many members have no record, adding a when-not-available signal, though it does not state an explicit 'use this when you need district contact info' imperative.

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