kr-elections-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEC_API_KEY | No | Legacy NEC API key (fallback). Used if NEC_API_KEY_DECODED and NEC_API_KEY_ENCODED are not set. | |
| NEC_API_KEY_DECODED | No | Decoded NEC service key. The server prefers this and can derive the encoded variant automatically. | |
| NEC_API_KEY_ENCODED | No | Encoded NEC service key. Not required if decoded key is provided. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| elections_resource |
TDQS
Scored across 16 tools
Several tools have overlapping names (e.g., get_district_results and get_district_summary; get_candidate_profile and get_candidate_policies). Diagnostic tools (diagnose_core_api_access, diagnose_full_api_access) are unrelated to elections, increasing confusion. Without descriptions, distinguishing purposes is challenging.
All tool names follow a verb_noun pattern in snake_case, using verbs like list, get, search, assemble, diagnose, match. The pattern is mostly consistent, though the variety of verbs (e.g., assemble, diagnose) slightly deviates from the more common list/get/search conventions.
16 tools is a reasonable count for an elections-related server. It covers multiple entities (elections, districts, parties, candidates) and includes some specialized tools. The count is slightly high but not excessive.
The tool set appears to support read and search operations only (no create, update, delete). The inclusion of diagnostic and 'krpoltext' tools suggests extraneous functionality unrelated to an elections data API. Gaps like updating candidate information or managing election results are likely to cause agent failures.