Parliament MCP (India)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RATE_LIMIT_BURST | No | Per-client rate limit burst size (default 20) when running as a web service. | |
| MCP_ALLOWED_HOSTS | No | Additional allowed hosts for the MCP SDK's DNS-rebinding protection; only localhost is allowed by default. | |
| MCP_ALLOWED_ORIGINS | No | Additional allowed browser origins for the MCP SDK's DNS-rebinding protection. | |
| TRUST_PROXY_HEADERS | No | Set to 1 behind a trusted reverse proxy so rate limiting keys on the real client IP. | |
| RATE_LIMIT_PER_MINUTE | No | Per-client rate limit in requests per minute (default 60) when running as a web service. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only data on India's current MPs (18th Lok Sabha and Rajya Sabha), parliamentary committees, and which committee is examining a bill. Data comes from PRS Legislative Research (CC BY 4.0) and must be credited as such. A committee role shows an MP works on a bill, not whether they support it. Each response states the date the data was retrieved.
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 |
|---|---|
| list_membersA | List current MPs. Filter by house ("Lok Sabha" or "Rajya Sabha"), state, or party. Paginated (limit 1–200). |
| search_membersA | Find MPs by name or constituency (partial match, max 50 results). |
| get_memberC | One MP's details, including the committees they sit on. |
| list_committeesA | All parliamentary committees with their chair and size. |
| get_committeeC | A committee's chair and full membership. |
| list_billsB | Bills currently tracked, with the committees examining them. |
| relevant_mps_for_billA | The MPs on the committee examining a bill. Accepts a PRS bill slug or part of the bill's title. |
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 7 tools
Most tools target distinct resources (members, committees, bills) and the list/get pairs are cleanly separated. The only real overlap is list_members vs search_members, which both answer 'find MPs' — one by structured filters, the other by partial text — and an agent could plausibly pick the wrong one for a name query. relevant_mps_for_bill is a join over list_bills/get_committee but its bill-centric framing makes its purpose clear.
Six of seven tools follow a consistent verb_noun snake_case pattern (list_members, get_member, list_committees, get_committee, list_bills, search_members). The exception is relevant_mps_for_bill, which is noun-phrase style rather than verb-first, but it remains readable and snake_case consistent.
Seven tools is a well-scoped set for a parliamentary data server: two list/get pairs for members and committees, a search, a bill listing, and one targeted cross-reference tool. Each tool has a distinct job and nothing feels padded.
Member and committee coverage is solid (list, search, get with committee membership), and bills can be listed and linked to committee members. However, there is no get_bill/detail tool for a specific bill (status, sponsors, text), so bill workflows dead-end at the list, and there is no committee search or bill-search operation.