hk-election-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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_gc_registered_electorsC | Get the number of registered electors in Hong Kong's geographical constituencies by year range |
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 1 tool
With only one tool, there is no possibility of overlap or misselection; its purpose (registered elector counts by year range) is unambiguous.
The single tool follows a clear snake_case verb_noun pattern (get_gc_registered_electors), so there is no inconsistency to penalize, though consistency is trivially satisfied.
A single tool is extremely thin for a server framed as an election data source; while the specific metric is narrow, one read-only lookup does not justify a standalone server.
The surface covers only one metric (registered electors by year range) and lacks obvious election-domain operations such as constituency breakdowns, turnout, candidates, or results, creating dead ends for most queries.