Skip to main content
Glama
seiichi3141

kokkai-giji-mcp

by seiichi3141

search_meetings_simple

Search Japanese Diet meeting records by keywords, speakers, dates, and more. Retrieve meeting details, matching speeches, and direct record URLs with up to 100 results per query.

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. It discloses the output is '簡易出力' (simple/basic output) and the 100-record cap, but doesn't describe pagination behavior, rate limits, authentication needs, or what fields the basic output contains. For a search/read-only tool this is partially adequate but leaves return-format uncertainty.

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 compact at roughly two sentences, first stating the purpose and then the output. It's appropriately sized and front-loaded with the primary purpose. Each sentence earns its place with useful information (search capability, basic output format, record cap).

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?

With 22 parameters, no output schema, and no annotations, the description is moderately complete. It explains the tool is a simple/basic search with a 100-record cap, but given the sheer number of parameters and sibling tools, the description could do more to explain the simple-vs-full distinction and how the output differs from search_speeches. The mention of '簡易出力' hints at this but doesn't elaborate.

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 coverage is 100%, so the baseline is 3. The description mentions AND search for 発言内容 and basic info/speech list retrieval, which adds high-level context. But it doesn't explain how the many search parameters combine with each other (e.g., whether issuing a query for 'any' plus issueID narrows or overrides), so it mostly relies on the well-documented 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 it searches Diet meetings with basic output format, retrieving basic meeting info and matching speech list. The '国会の会議を検索します' gives a clear verb+resource. It distinguishes from siblings via '簡易出力' (simple output format), though it doesn't explicitly contrast with search_meetings_full or search_speeches by name.

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 usage for searching meetings with basic output, and '最大100件まで取得可能' gives a key constraint. However, it doesn't explicitly state when to use this vs the 'full' variant or when to prefer search_speeches instead. No exclusions or alternatives are named.

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