Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_legislator_propose_bills

Retrieves bills proposed by a specific legislator in the Taiwan Legislative Yuan. Filter by term, name, bill status, and other criteria.

Instructions

取得委員為提案人的法案列表。

Args:
    term: 屆,例:11
    name: 委員姓名,例:韓國瑜
    bill_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
termYes屆,例:11
nameYes委員姓名,例:韓國瑜
bill_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 are provided, so the description carries full burden. It describes the basic operation and mentions pagination parameters (page, limit) but does not disclose pagination behavior, rate limits, authentication needs, or error conditions beyond a general '例外時回傳中文錯誤訊息字串'. The description is adequate but not rich in behavioral details.

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 quite long, largely repeating parameter details already present in the schema. The first sentence is a clear purpose statement, but the parameter list is verbose and redundant. It could be more concise by omitting the parameter list or referencing the schema.

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?

Given the tool's complexity (20 parameters) and that the schema covers all parameters fully and an output schema exists, the description is adequate. It states the return format (JSON string) and basic error behavior. It does not explain parameter interactions but is sufficient for an agent to understand the tool's core functionality.

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

Parameters4/5

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

The input schema has 100% description coverage, so baseline is 3. The description adds illustrative examples for each parameter (e.g., '例:11' for term, '例:韓國瑜' for name) and a recommendation for limit ('建議不超過100'). This provides extra context beyond the schema descriptions, enhancing understanding.

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?

The description clearly states the tool's purpose: '取得委員為提案人的法案列表' (Get the list of bills where the committee member is the proposer). It specifies the verb (取得/get) and resource (委員為提案人的法案列表/bills where legislator is proposer), distinguishing it from siblings like get_legislator_cosign_bills (bills where cosigner).

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 does not explicitly provide when or when not to use this tool or mention alternatives. The purpose implies usage for bills proposed by a specific legislator, but no exclusions or comparisons with similar tools (e.g., get_legislator_cosign_bills) are given. Guidance is only implied.

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