Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

by narumiruna

get_legislator_interpellations

Retrieve the list of interpellations where a specified legislator is the interpellation member, filtering by term, session, and meeting code.

Instructions

取得委員為質詢委員的質詢列表。

Args:
    term: 屆期,必填,例:11
    name: 委員姓名,必填,例:韓國瑜
    interpellation_member: 質詢委員姓名,例:羅智強
    term_query: 查詢條件中的屆,例:10
    session: 會期,例:2
    meeting_code: 會議代碼,例:院會-11-2-6
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式,包含委員為質詢委員的質詢資料。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes委員姓名,必填,例:韓國瑜
pageNo頁數,預設1
termYes屆,必填,例:11
limitNo每頁筆數,預設20,建議不超過100
sessionNo會期,例:2
term_queryNo查詢條件中的屆,例:10
meeting_codeNo會議代碼,例:院會-11-2-6
output_fieldsNo自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)
interpellation_memberNo質詢委員姓名,例:羅智強

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

無註解,描述必須承載行為揭露。描述提及傳回 JSON 格式及錯誤時傳回中文訊息,但未說明是否為唯讀、是否需要權限、分頁行為細節或其他副作用。相較於純粹的參數說明,僅增加少量行為資訊。

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

描述簡潔,結構分明(Arg、Returns、Raises),資訊優先放置於開頭,無冗詞贅字,易於閱讀。

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?

工具參數多達 9 個,描述未說明關鍵參數之間的關係(如 term 與 term_query 的差異、name 與 interpellation_member 的用途),也未提供使用情境或與其他工具的對比。輸出 schema 雖存在,但描述本身對複雜度而言仍顯不足。

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 對所有參數皆有描述,覆蓋率 100%,因此基準分為 3。描述中的 Args 段落重複了 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?

描述明確指出取得質詢列表,並限定委員為質詢委員,清楚區分於其他質詢相關工具。動詞 'get' 與資源 'interpellations' 具體,且與兄弟工具(如 list_interpellations、get_meet_interpellations)有別。

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?

描述未提供任何使用時機或與替代工具的比較,亦未說明當與其他質詢查詢工具搭配時該如何選擇。僅有功能說明,缺乏實用的指引。

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