le-bills-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LE_CACHE_DIR | No | Optional directory to save the bill search index in, so it survives restarts (about 1.2 MB per session). If unset, the index is kept in memory only. | |
| LE_UTAH_TOKEN | No | GLEN developer token. Enables get_utah_code, get_constitution, get_legislative_rule, and get_meeting_agenda. | |
| LE_MAX_RESPONSE_CHARS | No | Default per-response character budget (500–20000). | 4000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Utah State Legislature data: bills, legislators, committees, meetings.
Sessions: '2026' or '2026GS' = general session; '2025S1' = first special session. Omit for the current/most recent general session. Bill numbers accept 'HB 1', 'H.B. 1', 'hb0001', 'SJR3'.
Context budget: every tool returns at most max_chars characters (default 4000). Long
results include next_offset; call again with offset=next_offset to page. Prefer
detail="brief" and narrow tools first. To study a bill's text: load_bill -> table of contents,
then read_bill_text(section=...) or find_in_bill(pattern) rather than reading everything.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_billA | Get a bill's metadata: title, sponsors, status, and (standard/full) its summary, subjects, affected code sections, versions. Does not include bill text - use load_bill for that. |
| get_bill_historyA | Action history of a bill (committee referrals, readings, votes with tallies as yeas-nays-absent, governor action) plus floor debate dates. By default returns the last 10 actions plus every vote action, oldest first. |
| get_bill_documentsA | List a bill's documents (bill text versions, fiscal notes, committee reports, transmittal letters) with absolute URLs. |
| load_billA | Load a bill's full text into the server's working memory and return only a table of contents (section ids, headings, sizes). The text stays server-side: read it piece by piece with read_bill_text or search it with find_in_bill. Up to 10 bills stay loaded. |
| read_bill_textA | Read a slice of a bill's text (loads the bill if needed). Amendments are marked [+inserted+] and [-deleted-]. Page with offset/next_offset. |
| find_in_billA | Search inside a bill's text and return only matching snippets with their section ids (loads the bill if needed). Use read_bill_text(section=..., offset=...) to read around a hit. |
| list_loaded_billsB | List bills currently loaded in working memory. |
| unload_billA | Remove a bill from working memory. |
| get_fiscal_noteA | Read a bill's fiscal note (estimated revenue/expenditure impact) as plain text, paged. |
| search_billsA | Keyword search over bill titles, subjects and summaries for a session. With an empty query, lists bills matching the subject/sponsor/status filters. The first search of a session starts building a local index in the background (~10 min, rate-limited); until it finishes, results cover passed bills (titles only) plus whatever has been indexed so far. |
| refresh_bill_indexA | Update the local search index for a session (only changed bills unless full=True), or check on a background build's progress. |
| list_billsA | List numbered bills in a session with last-update times (titles included when the search index has been built). Use get_bill or search_bills for details. |
| list_passed_billsB | Bills that passed the Legislature in a session (2016+), with governor action. |
| list_bill_requestsB | Unnumbered bill requests (drafts being prepared) for a session, with titles and sponsor ids. |
| list_legislatorsA | List current Utah legislators, filterable by chamber, party, district or county. |
| get_legislatorA | Get one legislator by id or name. Returns candidates if the name is ambiguous. |
| list_committeesB | List legislative committees with chair, member count and next meeting (UTC). |
| get_committeeA | Get a committee's members (with positions) and scheduled meetings. |
| get_meeting_calendarC | Upcoming legislative meetings (times in UTC; Utah is UTC-7/-6). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools have clearly distinct purposes, especially across bills, legislators, committees, and bill-text working memory. There is some overlap between list_bills and search_bills with an empty query, and several bill-document/text tools are adjacent, but descriptions mostly resolve these boundaries.
All tool names consistently use snake_case with predictable verb_noun patterns such as get_bill, list_committees, search_bills, load_bill, and unload_bill. The naming is easy to scan and follows the same convention throughout.
At 19 tools, the surface is slightly above the typical sweet spot but reasonable given the domain spans bills, bill text, legislators, committees, and meetings. Each tool appears to serve a specific role, though a few could potentially be consolidated.
Coverage is strong for a legislative bill server: metadata, history, documents, text access, fiscal notes, search, passed bills, bill requests, legislators, committees, and meetings are all represented. Minor gaps may exist around version comparison or detailed roll-call lookup, but core workflows are covered.