Skip to main content
Glama
seiichi3141

kokkai-giji-mcp

by seiichi3141

search_meetings_full

Search Japanese Diet meetings and retrieve full meeting records with complete speech transcripts. Filter by keywords, speakers, dates, sessions, and house to find and access detailed proceedings data.

Instructions

国会の会議を検索します(会議単位出力)。会議の全発言本文を含む詳細データを取得します。最大10件まで取得可能。

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-10、デフォルト3)
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 of behavioral disclosure. The description mentions it returns '会議の全発言本文を含む詳細データ' (full speech text included), which adds some behavioral context. However, it does not disclose rate limits, auth requirements, cost implications of full-text retrieval, or what the response structure looks like beyond noting detailed data.

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 a concise single sentence with the key information front-loaded. It efficiently states purpose, output format, and record limit in one compact sentence. No wasted words, but it could have used the space to add sibling differentiation.

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?

This is a complex tool with 22 parameters and no output schema. The description mentions '詳細データ' (detailed data) but doesn't elaborate on what the output looks like or how the many date/range/session parameters interact. While the schema covers all parameter descriptions, the description itself provides limited guidance on how to combine parameters effectively for a search with this many options.

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 documents all 22 parameters with descriptions. The description adds only the 10-record maximum limit which is also in the schema's maximumRecords parameter (maximum: 10). The description's one extra note about meeting-unit output helps frame parameter semantics but adds nothing beyond the schema.

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?

The description states '国会の会議を検索します(会議単位出力)' with a specific verb (検索 - search), resource (国会の会議 - Diet meetings), and output unit (会議単位 - meeting-unit). It distinguishes from search_speeches by noting meeting-unit output order. However, differentiation from search_meetings_simple is only implicit through the word 'full' in the tool name rather than explicit in the description.

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 notes '最大10件まで取得可能' (max 10 records retrievable), giving some practical usage constraint. However, there is no explicit guidance on when to use this tool vs. search_meetings_simple or search_speeches. The sibling differentiation is implied through the 'full' name and meeting-unit output but not 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