Skip to main content
Glama
kyusik-yang

open-assembly-mcp

by kyusik-yang

get_bill_committee_review

Retrieve committee meeting records for a specific bill, showing dates and results for each session.

Instructions

특정 의안의 위원회 심사 회의정보를 조회합니다.

Get the individual committee meeting records at which a specific bill was reviewed. Returns one row per committee meeting, with date and result for each session.

NOT this tool: • For the HIGH-LEVEL processing timeline (committee referral date, plenary vote date) → use get_bill_review (which takes BILL_NO, not BILL_ID)

When to use: • To see exactly when and how many times a bill was discussed in committee. • Combined with get_bill_review for a complete legislative timeline.

IMPORTANT — requires BILL_ID, not BILL_NO: • BILL_ID looks like "PRC_..." — get it from search_bills, get_pending_bills, get_vote_results, or get_bill_review • BILL_NO is the 7-digit public number — WRONG for this tool

Args: bill_id: 의안ID — 필수 (예: "PRC_T2M6W0F2I1W2T1X7T4K2Q5A9J4P2M5")

Returns: meetings: 위원회 심사 회의 목록 — BILL_ID, BILL_NM, CMIT_NM(위원회), MTG_DT(회의일), SESS_NO(회기), PROC_RESULT(결과) 등 count: 반환된 회의 수 total_count: 전체 건수

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bill_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries burden. It's a read operation implied by 'get' and description, and it details return fields. Lacks explicit safety info but sufficient for a read-only 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?

Structured with sections, bilingual, clear. Slightly verbose due to bilingualism but front-loaded with purpose. Efficient overall.

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

Completeness5/5

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

Given output schema exists, description adequately explains return fields and usage context. Provides complete guidance for a single-parameter tool with no gaps.

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

Parameters5/5

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

Schema coverage 0% but description includes an 'Args' section explaining bill_id in detail, with format example and critical distinction from BILL_NO. Adds significant value beyond schema.

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

Purpose5/5

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

Clearly states it retrieves committee meeting records for a specific bill. Distinguishes from sibling get_bill_review by specifying it returns individual meeting records rather than high-level timeline.

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

Usage Guidelines5/5

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

Explicitly says when to use (to see committee discussions) and when not (for high-level timeline, use get_bill_review). Also warns about BILL_ID vs BILL_NO, providing alternatives.

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/kyusik-yang/open-assembly-mcp'

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