Japan Parliament Search MCP
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_speechesA | 日本の国会会議録（1947年〜最新）から発言を全文検索する。大臣答弁・質疑・政府見解の一次資料を、発言者・院・会議名・期間で絞り込める。政策調査・報道・ロビイング・コンプライアンス確認に有用。デフォルトは発言の冒頭抜粋を返す。full_text=trueで発言全文を取得（長い場合がある）。 |
| search_meetingsA | キーワードを含む国会の会議（本会議・委員会）単位で検索する。どの委員会でいつ議論されたかの全体像を掴むのに使う。個別の発言内容はsearch_speechesで取得する。 |
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 2 tools
The two tools have clearly distinct purposes: search_meetings focuses on meeting-level search to understand which committee discussed what, while search_speeches provides full-text speech search. There is no overlap in functionality.
Both tools follow a consistent 'verb_noun' pattern with 'search_' prefix plus a plural noun (meetings, speeches), making the naming predictable and clear.
Only 2 tools is slightly below the typical 3-15 range, but for a focused task like searching Japanese parliament records, this minimal set can be sufficient if it covers the core use cases of meeting discovery and speech retrieval.
The tools cover primary search needs but lack additional capabilities like retrieving individual meeting details, filtering by exact dates, or exporting results. Minor gaps that agents can work around with careful queries.