Skip to main content
Glama

list_legislators

Read-only

Retrieve current Utah legislators and filter results by chamber, party, district, or county to identify representatives for a specific area or political group.

Instructions

List current Utah legislators, filterable by chamber, party, district or county.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_legislators"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax items to return (1-50).
partyNo'R' or 'D'.
countyNoOnly legislators whose district includes this county.
detailNobrief = one line per item; standard adds summaries; full adds everything.brief
offsetNoStart position for paging; use next_offset from a prior call.
chamberNo'H' House or 'S' Senate.
districtNoDistrict number.
max_charsNoCharacter budget for this response (500-20000). Defaults to the server setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=true, so the safety profile is covered. The description adds only the filterable fields and says nothing about paging behavior, response size budgeting (max_chars), or how 'current' membership is determined, all of which are left to the schema to explain.

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 with the resource first and the filterable dimensions second, containing no filler. It is slightly terse for an eight-parameter tool, but nothing in it is wasted.

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?

For a read-only filtered list with fully documented parameters, the description covers what the tool returns at a high level (legislators, by chamber/party/district/county). With no output schema, the return shape is only hinted at through the schema's detail enum rather than described here, which is the main residual gap.

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%, so limit, offset, detail, chamber, party, district, county, and max_chars are all documented inline with enums and defaults. The description's mention of the four filter fields restates what the schema already says, so no meaning is added beyond it; baseline 3 applies.

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 states a specific verb and resource ('List current Utah legislators') plus the filter dimensions, so an agent can distinguish it from the singular get_legislator sibling by plurality and scope. It does not name an alternative explicitly, but the purpose is unambiguous.

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: use this to enumerate legislators with optional chamber/party/district/county filters. There is no explicit when-to-use versus when-not, and no pointer to get_legislator for fetching one member's full record, so the agent must infer the routing.

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