Skip to main content
Glama

List elected officials

list_officials
Read-onlyIdempotent

Who serves on a city council — mayors and council members — looked up by city, state, or name.

Returns the CURRENT ELECTED roster by default: people in office right now, no appointed board members, no staff. Answer 'who represents me' straight from this — no need to hedge about whether someone still holds the seat. Each row carries role, status, and term dates.

WHEN: First stop for 'who represents…' questions, and the prerequisite for any search_by_official / track_position call (both need a UUID this tool returns). WHEN NOT: For voting records use track_position; for quotes use search_by_official, with an id from here.

Set include_former for historical questions ('who was mayor in 2024?') or when reading an older meeting whose speakers have since left office — an official_id you got elsewhere may belong to someone no longer seated. Set include_appointed for planning commissioners and city staff.

EXAMPLES: { "city": "lehi-ut" } — the sitting Lehi council { "city": "lehi-ut", "include_former": true } — plus everyone who has left office { "state": "UT", "name_contains": "binns" } — find 'Paul Binns' across Utah { "city": "lehi-ut" } then pivot to track_position with one of the returned ids

Input Schema

NameRequiredDescriptionDefault
cityNoCity slug (e.g. 'lehi-ut'). Strongly recommended — narrows the response to one city's roster. Without it, returns officials across every city you have access to (can be hundreds of rows).
limitNoMax rows returned. Default 50.
stateNoTwo-letter US state abbreviation (e.g. 'UT', 'CA'). Use when you want every city in a state. Case-insensitive.
name_containsNoCase-insensitive substring match on the official's name (e.g. 'binns' matches 'Paul Binns'). Combine with `city` or `state` to look up someone specific.
include_formerNoInclude officials who have left office. Default false — 'who represents me' means the sitting roster. Turn on for historical questions ('who was mayor in 2024?') or when reading an old meeting where the speakers are no longer seated.
include_appointedNoInclude appointed board members (planning commissioners and the like) and city staff (administrator, attorney, recorder). Default false — they are not elected and do not vote on the council.

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of officials returned in this response.
officialsYesOfficials matching the filters — by default the CURRENT ELECTED roster, so this answers 'who serves on the council' directly. Public-record data from city government websites.
citiesQueriedYesNumber of cities scanned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive semantics, and the description adds real behavior beyond them: the default roster excludes appointed members and staff, former officials require an explicit flag, and a stale official_id may point to someone no longer seated. The mention of role/status/term-date columns is mildly redundant given the output schema exists, keeping this just short of top marks.

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?

Well front-loaded with the most decision-relevant fact first (current roster by default), then WHEN/WHEN NOT, then examples. It is longer than strictly necessary because the include_former and include_appointed rationales are largely duplicated in the schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, annotation-rich tool with an output schema, the description covers purpose, default filtering behavior, flag semantics, prerequisites, and sibling routing without needing to explain return values. Nothing an agent needs in order to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds intent-level meaning: include_former is framed as the historical/old-meeting switch, include_appointed as the planning-commissioner/staff switch. The EXAMPLES block demonstrates realistic parameter combinations (city+include_former, state+name_contains) that the schema alone does not convey.

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 and resource — looking up who serves on a city council — and pins the default scope precisely (current elected officials, no appointed members, no staff). An agent can distinguish it from track_position and search_by_official without reading a schema.

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

Usage Guidelines5/5

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

Explicit WHEN and WHEN NOT sections name the conditions and the alternatives: track_position for voting records, search_by_official for quotes. It also declares a prerequisite relationship (both siblings need a UUID this tool returns), which is exactly the routing information an agent needs.

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