Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

by narumiruna

list_meets

Find and filter Taiwan Legislative Yuan meetings by term, session, date, committee, or attendee, returning JSON-formatted lists for easy analysis.

Instructions

列出立法院會議列表。

Args:
    term: 屆,例:11
    meeting_code: 會議代碼,例:院會-11-2-6
    session: 會期,例:2
    meeting_type: 會議種類,例:院會
    meeting_attendee: 出席委員,例:陳秀寳
    date: 日期,格式:YYYY-MM-DD,例:2024-10-25
    committee_code: 委員會代號,例:23
    meeting_id: 會議編號,例:2024102368
    meeting_bills_bill_no: 關係文書議案編號,例:202110071090000
    meeting_bills_law_no: 關係文書法律編號,例:01177
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的會議列表。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo日期,格式:YYYY-MM-DD,例:2024-10-25
pageNo頁數,預設1
termNo屆,例:11
limitNo每頁筆數,預設20,建議不超過100
sessionNo會期,例:2
meeting_idNo會議編號,例:2024102368
meeting_codeNo會議代碼,例:院會-11-2-6
meeting_typeNo會議種類,例:院會
output_fieldsNo自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)
committee_codeNo委員會代號,例:23
meeting_attendeeNo出席委員,例:陳秀寳
meeting_bills_law_noNo關係文書法律編號,例:01177
meeting_bills_bill_noNo關係文書議案編號,例:202110071090000

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description must disclose behaviors. It minimally states return type (JSON string) and error handling, but lacks details on pagination, rate limits, or what happens with invalid filters.

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 a lengthy parameter list with examples; it is verbose but structurally clear. It could be more concise by grouping related parameters.

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 13 parameters and presence of an output schema, the description adequately lists inputs and return type but lacks usage advice or complete behavioral context.

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 schema already explains each parameter. The description repeats the same examples, adding no new semantic value beyond the schema.

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 tool lists meetings of the Legislative Yuan, with many filtering parameters. However, it does not explicitly differentiate itself from sibling tools like get_meet, which retrieves a single meeting.

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. The description only lists parameters without any usage context or prerequisites.

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