Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_bills

Retrieve legislative bills from Taiwan's Legislative Yuan using filters like term, session, bill type, status, proposer, and more. Provides paginated JSON results.

Instructions

列出立法院議案列表。

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

Returns:
    str: JSON 格式的議案查詢結果。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNo屆,例:11
sessionNo會期,例:2
bill_flow_statusNo議案流程狀態,如:交付審查、三讀
bill_typeNo議案類別,如:法律案、預算案
proposerNo提案人姓名
cosignerNo連署人姓名
law_numberNo法律編號
bill_statusNo議案狀態,如:交付審查、三讀、排入院會
meeting_codeNo會議代碼
proposal_sourceNo提案來源,如:委員提案、政府提案
bill_numberNo議案編號
proposal_numberNo提案編號
reference_numberNo字號
article_numberNo法條編號
proposal_dateNo提案日期,格式:YYYY-MM-DD
proposal_unit_or_memberNo提案單位或提案委員
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?

The description discloses the return format (JSON string) and error handling (Chinese error messages). It also mentions pagination parameters (page, limit). However, it does not explicitly state that the tool is read-only, nor does it address potential side effects, rate limits, or authentication requirements. Given no annotations, the description provides basic but incomplete behavioral insight.

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

Conciseness2/5

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

The description is verbose, listing all 19 parameters in a bullet format that mirrors the schema. While structured, it could be significantly shortened by omitting the parameter list since the schema already provides that information. The first sentence is concise, but the rest adds bulk without value.

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 optional parameters) and the presence of an output schema, the description covers pagination, error handling, and return format. However, it does not explain which parameters are typically used together or how to construct a meaningful query, leaving the agent to guess at common use cases. It is minimally complete.

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 baseline is 3. The description largely repeats the parameter descriptions from the schema, adding only minor additional context (e.g., date format). It does not significantly enhance understanding beyond what the schema already provides.

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 the verb+resource: '列出立法院議案列表' (list bills of the Legislative Yuan). It explicitly lists all parameters, making the purpose evident. However, it does not differentiate from sibling tools like list_laws or list_gazettes, reducing clarity in the broader toolset.

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 is provided on when to use this tool versus alternatives, nor are there any conditions or exclusions mentioned. The description simply states what the tool does, leaving the agent to infer usage context without explicit direction.

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