Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_law_bills

Get legislative bills related to a specific law. Filter by term, session, bill status, proposer, and more to find relevant bills from Taiwan's Legislative Yuan.

Instructions

取得特定法律相關的議案列表。

Args:
    law_id: 法律編號,必填,例:09200015
    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
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式,包含該法律相關的議案資訊。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
law_idYes法律編號,必填,例:09200015
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
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?

No annotations provided; description carries the burden. It describes pagination (page, limit) and error handling (returns error string on exception), but does not disclose read-only nature, authentication needs, or other side effects. Some behavioral info is present but not comprehensive.

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 verbose due to duplicating parameter descriptions from the schema. While structured (Args, Returns, Raises), it could be more concise by summarizing parameter categories or omitting redundant details.

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

Completeness4/5

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

Despite length, the description covers purpose, all parameters with defaults, return format (JSON), and error handling. With an output schema present, detailed return info is optional. Adequate for a complex tool with 19 parameters.

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 Args section replicates the schema descriptions without adding new meaning. Baseline of 3 is appropriate as the description adds no semantic value beyond the 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?

Description clearly states the tool retrieves a list of bills related to a specific law (取得特定法律相關的議案列表). The verb 'get' and resource 'law bills' are explicit, distinguishing it from sibling tools like get_bill (single bill) or list_bills (all bills).

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

Usage Guidelines4/5

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

The description implies use when you need bills for a given law_id (required), but lacks explicit guidance on when not to use or alternative tools. The parameter list and required law_id provide clear context, but no direct comparison to siblings.

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