Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_legislator_cosign_bills

Retrieve a list of bills co-signed by a specific legislator. Filter by term, session, bill type, status, and other criteria to find relevant legislation.

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
Behavior2/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 states return type (JSON string) and error format (Chinese messages), but does not disclose side effects, authentication needs, rate limits, or data freshness. For a read operation, this is minimal but acceptable.

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 docstring format, most of which are direct copies from the schema. The purpose statement is concise, but the parameter list is redundant and could be shortened. The structure (args, returns, raises) is clear but inefficient.

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 20 parameters and an output schema (present but not shown), the description states the purpose, return format, and error handling. However, it does not explain how combining multiple filters works, pagination behavior beyond parameter defaults, or clarify the output structure. It is adequate but has gaps.

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 coverage is 100%, so the schema already describes all parameters. The description essentially repeats the parameter descriptions from the schema (e.g., 'term: 屆,例:11') without adding new semantic meaning. Therefore it adds minimal 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?

The description begins with '取得委員為連署人的法案列表', which clearly states the verb (取得, get) and resource (法案列表, bill list) with specific scope (委員為連署人, legislator as co-signer). This distinguishes it from sibling tools like get_legislator_propose_bills (for bills proposed) and get_bill (for a single bill).

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 implies usage for retrieving bills co-signed by a legislator, but it does not explicitly state when to use this tool versus alternatives such as get_legislator_propose_bills or list_bills. No exclusions or alternative tool names are mentioned.

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