Korean Bill & Debate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KBD_DATA_DIR | No | Override default cache directory (default: ~/.local/share/korean-bill-debate-mcp) | ~/.local/share/korean-bill-debate-mcp |
| ASSEMBLY_OPEN_API_KEY | Yes | Your Open Assembly API key from https://open.assembly.go.kr/ |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_speechesB | Search official speeches in Korean or English. |
| get_speechD | – |
| get_speech_contextD | – |
| list_committeesD | – |
| list_meetingsC | Query official meeting metadata for the requested scope and list cached candidates. |
| search_billsA | Search live bills from a Korean or English request. |
| get_bill_statusA | Refresh one bill's status and attach its official expert review report when available. |
| explore_issueA | Return one detailed, answer-ready review across every requested legislative stage. |
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 8 tools
The get/search/list verbs give some separation, but four of eight tools (get_speech, get_speech_context, list_committees, list_meetings) ship with empty descriptions, forcing the agent to guess their boundary from the name alone. Worse, explore_issue explicitly performs bill, meeting, and speech discovery and warns against calling the discovery tools first, so its boundary with search_bills/search_speeches/list_meetings is defined only by prose the agent must parse mid-task.
Every name is snake_case verb_noun (get_speech, search_speeches, list_committees, get_bill_status, explore_issue), with no camelCase or bare nouns mixed in. The verb vocabulary (get/search/list/explore) is applied predictably: get for single retrieval, search for queries, list for enumerations.
Eight tools is a sensible size for a legislative research domain, and each named tool maps to a recognizable resource. However, explore_issue is a mega-tool that subsumes much of search_speeches, search_bills, list_meetings, and get_bill_status, so a few tools earn only a marginal claim on their own existence.
Speeches, context, committees, meetings, bills, and status are covered, but there is no way to fetch a specific meeting's detail/minutes or a committee's page directly, so list_enumeration tools dead-end. The descriptions repeatedly route the agent to a durable research workflow via start_research, yet no such tool exists in this set, leaving an advertised but unreachable path.