Skip to main content
Glama
seiichi3141

kokkai-giji-mcp

by seiichi3141

search_speeches

Search Japanese Diet meeting speeches by keyword, speaker, session, date, and other filters to retrieve up to 100 individual speech records and their direct URLs.

Instructions

国会の発言を検索します(発言単位出力)。個別の発言本文を取得します。最大100件まで取得可能。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anyNo発言内容の検索キーワード。半角スペース区切りでAND検索
fromNo開会日付/始点(YYYY-MM-DD形式)
untilNo開会日付/終点(YYYY-MM-DD形式)
closingNo閉会中の会議録に限定(デフォルト:false)
issueIDNo会議録ID(21桁の英数字)
issueToNo号数To(終了号)
speakerNo発言者名。半角スペース区切りでOR検索
speechIDNo発言ID(例:100105254X00119470520_000)
issueFromNo号数From(開始号)
sessionToNo国会回次To(終了回)
nameOfHouseNo院名(衆議院、参議院、両院、両院協議会)
searchRangeNo検索対象箇所(冒頭、本文、冒頭・本文)
sessionFromNo国会回次From(開始回)
speakerRoleNo発言者役割(証人、参考人、公述人)
startRecordNo取得開始位置(デフォルト1)
speakerGroupNo発言者所属会派(部分一致)
speechNumberNo発言番号(0以上の整数)
nameOfMeetingNo会議名(例:本会議、予算委員会)。半角スペース区切りでOR検索
maximumRecordsNo最大取得件数(1-100、デフォルト30)
speakerPositionNo発言者肩書き(部分一致)
contentsAndIndexNo目次・索引に限定(デフォルト:false)
supplementAndAppendixNo追録・附録に限定(デフォルト:false)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. The description notes the 100-record maximum and per-speech output unit, which is useful. However, for a search/search tool with 22 parameters, it doesn't disclose pagination behavior, result ordering, error behavior, or whether results are returned in chronological order. The completeness notes are thin for such a complex tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences. It front-loads the core purpose (search speeches), adds output granularity (per-speech unit), and caps expectations with the 100-record limit. No wasteful content. Appropriate for a tool whose heavy lifting is delegated to the comprehensively documented schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 22-parameter tool with no output schema and no annotations, the description is arguably thin. However, the schema is 100% documented, which mitigates the parameter burden. The description confirms output granularity and the cap, which are the biggest unknowns. It could benefit from noting result ordering, but the core usage is adequately conveyed given the schema's thoroughness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 22 parameters. Baseline is 3. The description adds nothing about parameter semantics beyond what the schema provides — it doesn't explain any parameter interactions or common filter combinations. Schema carries the full weight, which is acceptable at the baseline level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states '検索します' (search) with clear resource being speeches (国会の発言), and notes it outputs per-speech units (発言単位出力) and returns individual speech text. This distinguishes from siblings search_meetings_simple and search_meetings_full which target meetings, but doesn't explicitly name them as alternatives. Purpose is clear and specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is for searching speech-level content (as opposed to meeting-level search in siblings), but does not explicitly state when to use this vs the meeting-search tools or provide exclusion criteria. No mention of when not to use it. Usage context is implied by the resource type rather than explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/seiichi3141/kokkai_giji_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server