Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_committee_meets

Retrieve committee meeting lists from the Legislative Yuan. Filter by committee code, term, session, date, and more to find specific meetings.

Instructions

取得委員會相關會議列表。

Args:
    comt_cd: 委員會代號,必填,例:15
    term: 屆期篩選,例:11
    meeting_code: 會議代碼
    session: 會期篩選,例:2
    meeting_type: 會議種類篩選,例:院會、委員會
    member: 會議資料.出席委員
    date: 日期,格式:YYYY-MM-DD
    committee_code: 委員會代號
    meet_id: 會議資料.會議編號
    bill_no: 議事網資料.關係文書.議案.議案編號
    law_number: 議事網資料.關係文書.議案.法律編號
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式,包含該委員會的相關會議資訊(會議編號、會議日期、出席委員等)。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comt_cdYes委員會代號,必填,例: 15
termNo屆,例: 11
meeting_codeNo會議代碼
sessionNo會期,例: 2
meeting_typeNo會議種類,例: 院會、委員會
memberNo會議資料.出席委員
dateNo日期,格式:YYYY-MM-DD
committee_codeNo委員會代號
meet_idNo會議資料.會議編號
bill_noNo議事網資料.關係文書.議案.議案編號
law_numberNo議事網資料.關係文書.議案.法律編號
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 bears full responsibility. It mentions that errors return Chinese error messages, but it does not disclose pagination behavior, rate limits, or whether the operation is read-only (likely, but not stated). For a tool with 14 parameters, this is insufficient.

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 lists all parameters in a readable bullet-like format, but it is somewhat lengthy and repetitive. It could be more concise by grouping related parameters or summarizing.

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 high parameter count (14), no annotations, and presence of an output schema, the description is adequate but lacks context on parameter interactions, required combinations, or typical usage patterns. It does not explain the overall workflow.

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 each parameter. The description repeats the schema descriptions almost verbatim, adding no new meaning. Per the baseline rule, a score of 3 is appropriate.

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 states '取得委員會相關會議列表' (get a list of committee-related meetings), clearly indicating the verb and resource. It distinguishes from siblings like 'get_meet' (likely a single meeting) and 'list_meets' (possibly all meetings), but the differentiation is not explicit.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not specify prerequisites, filters, or scenarios where this tool is preferred over other meeting-related tools.

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