Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_meet_bills

Retrieve bills within a legislative meeting using meeting ID and optional filters like term, session, bill type, proposer, or status.

Instructions

取得會議內的議案列表。

Args:
    meet_id: 會議代碼,例:院會-11-2-3
    term: 屆,例:11
    session: 會期,例:2
    bill_flow_status: 議案流程狀態,如:交付審查、三讀
    bill_type: 議案類別,如:法律案、預算案
    proposer: 提案人姓名
    co_proposer: 連署人姓名
    law_number: 法律編號
    bill_status: 議案狀態,如:交付審查、三讀、排入院會
    meeting_code: 會議代碼
    proposal_source: 提案來源,如:委員提案、政府提案
    bill_number: 議案編號
    proposal_number: 提案編號
    reference_number: 字號
    article_number: 法條編號
    proposal_date: 提案日期,格式:YYYY-MM-DD
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的會議內議案資料。

Raises:
    例外時回傳中文錯誤訊息字串。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meet_idYes會議代碼,例:院會-11-2-3
termNo屆,例:11
sessionNo會期,例:2
bill_flow_statusNo議案流程狀態,如:交付審查、三讀
bill_typeNo議案類別,如:法律案、預算案
proposerNo提案人姓名
co_proposerNo連署人姓名
law_numberNo法律編號
bill_statusNo議案狀態,如:交付審查、三讀、排入院會
meeting_codeNo會議代碼
proposal_sourceNo提案來源,如:委員提案、政府提案
bill_numberNo議案編號
proposal_numberNo提案編號
reference_numberNo字號
article_numberNo法條編號
proposal_dateNo提案日期,格式:YYYY-MM-DD
pageNo頁數,預設1
limitNo每頁筆數,預設20,建議不超過100
output_fieldsNo自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions the return format (JSON string) and error handling (Chinese error messages), but lacks details on side effects, permissions, or behavior when parameters are invalid (e.g., non-existent meet_id). It is adequate but not exhaustive.

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

Conciseness3/5

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

The description is structured with clear sections (Args, Returns, Raises) and a concise opening sentence. However, it is lengthy due to listing all 19 parameters, many of which are already documented in the schema, making it less concise than ideal.

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?

Given the complexity (19 parameters, no annotations), the description covers basic usage but lacks contextual details like filtering logic, relationship between parameters (e.g., meet_id vs meeting_code), or pagination beyond defaults. The output schema likely helps, but the description does not explain the returned JSON structure.

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%, and the description's parameter documentation essentially duplicates the schema descriptions. Thus, it adds minimal new meaning beyond the schema, resulting in the baseline score of 3.

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 clearly states '取得會議內的議案列表' (get list of bills in a meeting), specifying the verb and resource. However, it does not explicitly differentiate from sibling tools like list_bills or get_meet, which could also return bills in a meeting context.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It only describes parameters, but does not explain scenarios where other tools might be more appropriate (e.g., list_bills for general bill search, get_bill for a single bill).

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/narumiruna/ly-mcp'

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