Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_legislator_interpellations

Retrieve interpellations made by a specific legislator in Taiwan's Legislative Yuan. Filter by term, session, or meeting code.

Instructions

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

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

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

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses return format (JSON string), error handling (Chinese error messages), and parameter details. However, it could mention that it is a read-only query and explain pagination behavior.

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?

The description is well-structured with Args and Returns sections, but it is slightly verbose. It could be more concise while retaining all necessary information.

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

Completeness4/5

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

Given the output schema exists, the description covers parameters and error handling. It lacks details on pagination behavior (total count, next page) but is otherwise complete for a list query tool.

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 adds minimal extra value beyond the schema, such as a recommendation for limit (不超過100) and default values for page and limit. This is adequate but not exceptional.

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 the verb '取得' (get) and the resource '質詢列表' (list of interpellations), and specifies the role '委員為質詢委員' (legislator as interpellator), distinguishing it from sibling tools like get_interpellation or list_interpellations.

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 querying interpellations where the given legislator is the interpellator, but it does not explicitly contrast with alternatives (e.g., get_meet_interpellations, list_interpellations) or provide when-not-to-use guidance.

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