Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_legislator_meets

Retrieve meetings attended by a specific legislator, with filters for term, session, date, committee, and meeting type.

Instructions

取得委員出席的會議列表。

Args:
    term: 屆,例:11
    name: 委員姓名,例:韓國瑜
    meet_term: 會議所屬屆期,例:11
    meeting_code: 會議代碼,例:院會-11-2-6
    session: 會期,例:2
    meeting_type: 會議種類,例:院會
    member: 出席委員,例:陳秀寳
    date: 日期,例:2024-10-25
    committee_code: 委員會代號,例:23
    meet_id: 會議編號,例:2024102368
    bill_no_nested: 關係文書議案編號,例:202110071090000
    law_number_nested: 關係文書法律編號,例:01177
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的委員出席會議列表。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes屆,例:11
nameYes委員姓名,例:韓國瑜
meet_termNo會議所屬屆期,例:11
meeting_codeNo會議代碼,例:院會-11-2-6
sessionNo會期,例:2
meeting_typeNo會議種類,例:院會
memberNo出席委員,例:陳秀寳
dateNo日期,例:2024-10-25
committee_codeNo委員會代號,例:23
meet_idNo會議編號,例:2024102368
bill_no_nestedNo關係文書議案編號,例:202110071090000
law_number_nestedNo關係文書法律編號,例:01177
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 must disclose behavioral traits. It only states the return type and error handling but omits safety (e.g., read-only), authentication needs, rate limits, or pagination behavior beyond parameter defaults. The 'Returns' section merely repeats the output format.

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 functional with clear 'Args', 'Returns', and 'Raises' sections. However, the parameter list is redundant with the schema and could be condensed. The initial sentence is concise, but the overall length is bloated by repetitive examples.

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

Completeness2/5

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

With 15 parameters, no annotations, and an output schema present, the description fails to explain parameter interactions or required combinations beyond the two mandatory ones. It does not clarify whether filters are additive or exclusive, leaving ambiguity for complex queries.

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 baseline is 3. The description repeats the same parameter examples and descriptions as the schema without adding new semantics (e.g., which parameters are filters vs. pagination, or how multi-parameter queries combine).

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 '取得委員出席的會議列表' (get list of meetings attended by legislators), specifying verb and resource. The tool name and description differentiate it from siblings like get_legislator (personal info) and get_meet (meeting details).

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 like get_committee_meets or get_meet. The description only lists parameters without any context about filtering precedence or typical use cases.

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