kokkai-giji-mcp
Related Servers
Alternatives to kokkai-giji-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables search, retrieval, and summarization of Japanese National Diet meeting minutes via MCP tools.81-
- FlicenseAqualityDmaintenanceProvides a structured interface to the Japanese National Diet Library's parliamentary proceedings API, allowing AI models to search and retrieve Diet meeting records and speeches.31-
- AlicenseAqualityCmaintenanceMCP server for searching Japanese Diet bills and committee Q\&A records via the NDL Kokkai API.411 npm1MIT
- AlicenseAqualityAmaintenanceMCP server for searching the National Diet Library of Japan (NDL Search), enabling Japanese-script bibliographic and article searches with rate limiting and attribution.61MIT
- FlicenseBqualityDmaintenanceMCP server for searching Japanese government procurement notices via the Kanpou API. Enables LLMs to search by date, keyword, or detailed criteria.31-
- AlicenseAqualityDmaintenanceMCP server for searching and retrieving Japanese laws from the e-Gov API, enabling natural language queries for legal information.313 npmMIT
TDQS
Scored across 3 tools
The three tools share a common search intent over the same domain (国会/kokkai meetings and speeches). search_meetings_simple vs search_meetings_full differ only in output verbosity (basic vs full text) and result limits, which is a subtle distinction agents may confuse. search_speeches is clearly distinct in granularity (speech-level vs meeting-level).
All tools follow a consistent verb_noun pattern starting with 'search_'. The three suffixes (meetings_simple, meetings_full, speeches) are semantically clear. The only minor inconsistency is mixing output-verbosity qualifiers (simple/full) with granularity (speeches) rather than a strictly uniform convention.
Three tools is on the low end but not unreasonable for a focused search-oriented MCP server. However, two of the three tools (meetings_simple and meetings_full) serve nearly the same purpose with just a verbosity difference, which feels somewhat redundant rather than distinct coverage.
The server covers search over meetings and speeches, but is missing common operations for a Japanese Diet (kokkai) domain such as searching by committee/session, retrieving a specific meeting or speech by ID, or pagination support beyond fixed maximums. The three search tools cover basic query needs but leave notable gaps in targeted retrieval.