Skip to main content
Glama

NHLA Liberty Ratings

legislator_votes

Read-onlyIdempotent

The roll calls NHLA scored in one session, how a legislator voted on each, and whether that matched NHLA's position. Optionally filtered to one bill.

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": {
      "legislator": "<legislator>"
    },
    "name": "legislator_votes"
  }
}

Input Schema

NameRequiredDescriptionDefault
billNolimit to one bill, e.g. HB609
yearNothe session; defaults to the most recent one they served
limitNohow many roll calls to return; default 50, maximum 200
legislatorYesa name, slug, personId or employeeNo

Output Schema

NameRequiredDescriptionDefault
urlNo
nameNo
slugNo
yearYes
foundYes
notesYes
tallyYes
totalYes
votesYes
sourceYes
chamberNo
summaryNo
personIdNo
returnedYes
truncatedYes
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the scoping fact that only NHLA-scored roll calls in one session are returned, which is useful context beyond annotations, but it says nothing about default session selection, result ordering, or truncation behavior.

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?

A single front-loaded sentence plus a short modifier, with no redundant or filler wording. The payload is stated first and the optional filter second, which is the right order for an agent scanning for relevance.

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 only four parameters, full schema coverage, and an output schema handling return values, the description needs mainly to state what data comes back and over what scope — which it does. Minor gaps around default session resolution and pagination-aware limits are acceptable given they are documented in the schema.

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% and every parameter (bill, year, limit, legislator) has its own description, so the baseline is 3. The description only echoes the bill filter and session scope already documented in the schema, adding no new meaning such as accepted legislator identifier formats or how year defaults are chosen.

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 names the specific resource — NHLA-scored roll calls, the legislator's vote on each, and whether it matched NHLA's position — which is a precise, distinctive payload. It is not a bare restatement of the name and is distinguishable in substance from 'legislator_record' and 'grade_key', though it never names those siblings to make the contrast explicit.

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 context is implied by the content description ('how a legislator voted on each'), and the phrase 'optionally filtered to one bill' signals a narrowing case. However, there is no explicit statement of when to use this versus legislator_record or grade_key, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources