Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_meet_interpellations

Retrieve interpellation records from a legislative meeting by meeting ID. Filter by member, term, session, or meeting code to narrow results.

Instructions

取得會議內的質詢列表。

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

Returns:
    str: JSON 格式的會議內質詢資料。

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

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses return type (JSON string) and error handling (Chinese error messages), but does not mention any side effects, authorization needs, rate limits, or pagination behavior beyond parameter defaults. Adequate but not rich.

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, Returns, and Raises sections, making it easy to scan. It is concise without unnecessary text, though some parameter descriptions repeat the schema exactly. Overall efficient for the information provided.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, one required) and presence of an output schema, the description adequately covers all aspects: parameter details, return format, and error handling. It is self-contained for an agent to understand usage without needing to inspect the output 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 description coverage is 100%, so baseline is 3. The description adds examples inline with parameter descriptions but largely mirrors the schema. It provides context for defaults (e.g., page=1, limit=20) but no additional semantic meaning beyond what's in the 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?

The description clearly states '取得會議內的質詢列表' (get list of interpellations within a meeting), specifying the action and resource. It distinguishes from sibling tools like get_interpellation (single interpellation) and list_interpellations (general list) by focusing on meeting context.

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 provides clear parameter details but does not explicitly state when to use this tool versus alternatives like get_interpellation or list_interpellations. Usage context is implied by the name and parameters, but no when-not-to-use or alternative guidance is given.

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