Knesset MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-bill-infoA | Get detailed information about a specific bill by its BillID, including initiators. |
| search-bills-by-nameA | Search bills by keyword in their name. Returns up to 20 most recent Knesset matches. |
| list-bills-by-statusA | List recent bills filtered by StatusID (from KNS_Status), ordered by LastUpdatedDate descending. Ordering uses LastUpdatedDate since the OData API does not expose per-stage transition dates on KNS_Bill. |
| list-recent-bills-by-stageA | List recent bills at a named legislative stage. Note: the Knesset combines 2nd and 3rd readings into one vote, so 'second-third-approved' is the closest proxy to 'passed second reading'. 'passed' = became law. |
| list-bills-by-typeB | List bills by type (private, government, or committee), optionally filtered by Knesset number, ordered by most recent update. |
| get-committee-infoC | Get information about a specific committee by its CommitteeID. |
| list-committeesB | List committees for a given Knesset number. |
| list-knesset-membersA | List Knesset members (MKs) with party (faction) affiliation for a given Knesset. Uses PositionID=54 on KNS_PersonToPosition, which is the row that carries FactionID/FactionName (PositionID=43 exists but has null faction fields). Optionally filter by factionId — use list-factions to discover IDs. Note: an MK who switched factions mid-term appears once per stint. |
| list-factionsA | List factions (parties) for a given Knesset number. Use the returned FactionID with list-knesset-members to get party rosters. |
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 9 tools
Each tool has a clearly distinct purpose: get-bill-info and get-committee-info target single entities; list-bills-by-status, list-bills-by-type, and list-recent-bills-by-stage provide different filtering; list-committees, list-factions, list-knesset-members each cover specific lists; search-bills-by-name is a keyword search. No overlap causes confusion.
All tool names follow a verb_noun_with_hyphens pattern. 'get-' is used for single-item retrieval, 'list-' for multiple items, and 'search-' for keyword search. The pattern is consistent and predictable across all 9 tools.
9 tools is appropriate for a parliamentary data server. It covers the main entities (bills, committees, factions, members) without being overwhelming or too sparse.
The tool set covers core CRUD-like queries (read-only) for bills, committees, factions, and members. Minor gaps include no dedicated get-faction or get-member tool, but list endpoints with filters largely fill these needs.