OpenTK Model Context Protocol Server
Related Servers
Alternatives to OpenTK Model Context Protocol Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides access to Dutch Parliament (Tweede Kamer) open data through MCP tools, enabling querying of parliamentary information via natural language.190 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides programmatic access to official German Bundestag parliamentary data, enabling LLMs to answer questions about legislation, voting records, and members.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Swedish Parliament open data through natural language.188 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to query and retrieve real-time open data, documents, protocols, and records from the Swedish Parliament (Riksdag) and Government Offices through 32 specialized MCP tools.31-
- AlicenseAqualityFmaintenanceEnables querying over 3,200 Dutch statutes (AVG, Wetboek van Strafrecht, Burgerlijk Wetboek, etc.) with verbatim, citation-grounded text from official sources, directly from MCP-compatible AI assistants.1842 npm13Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides access to the Norwegian Parliament's open data via Stortinget's API, enabling querying of parliamentary information through natural language.175 npmMIT
TDQS
Scored across 14 tools
Most tools have distinct purposes, but there is notable overlap between search_tk, search_tk_filtered, and search_by_category, which could confuse agents about which to use for document searches. Additionally, get_document_details and get_document_content serve different functions but might be misselected due to similar naming and domain overlap. The descriptions help clarify, but the boundaries are not perfectly clear.
The naming follows a consistent verb_noun pattern (e.g., get_overview, list_persons, search_tk) with minor deviations like birthdays_today (noun_verb) and get_document_links (which could be named more consistently as get_document_links or similar). Overall, the pattern is readable and mostly predictable, with only a few inconsistencies.
With 14 tools, the count is well-scoped for a parliamentary data server, covering MPs, committees, documents, activities, and searches. Each tool appears to serve a specific purpose without redundancy, fitting within the typical 3-15 range for such a domain.
The tool set provides comprehensive coverage for parliamentary data, including CRUD-like operations for documents (get, search), MPs (list, get photo), committees (list, get details), and activities (get overview, get upcoming). Minor gaps include no explicit update or delete tools, but this is reasonable for a read-only data source, and agents can work around this with the available search and retrieval tools.