Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_legislators

Retrieve a list of legislators from Taiwan's Legislative Yuan with filters for term, party, district, name, and custom field selection. Supports pagination for efficient data access.

Instructions

取得立法委員列表。

Args:
    term: 屆,例:11
    party: 黨籍,例:民主進步黨
    district_name: 選區名稱,例:臺南市第6選舉區
    legislator_id: 歷屆立法委員編號,例:1160
    legislator_name: 委員姓名,例:韓國瑜
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的立法委員列表。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNo屆,例:11
partyNo黨籍,例:民主進步黨
district_nameNo選區名稱,例:臺南市第6選舉區
legislator_idNo歷屆立法委員編號,例:1160
legislator_nameNo委員姓名,例:韓國瑜
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 exist, so the description must convey behavioral traits. It mentions returning a JSON string and raising exceptions, but lacks details on pagination behavior, data freshness, or side effects. Basic transparency is present.

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 structured with an intro, parameter list, returns, and raises. It is front-loaded with the purpose. Some parameter details could be streamlined, but overall clear.

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 8 optional parameters and an output schema (true but not shown), the description covers returns and error messages. It lacks details on filtering logic (AND/OR) or output field names, but is adequate for use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 8 parameters are described in the schema (100% coverage). The description adds value by providing concrete examples for each parameter and recommending a limit (not exceed 100), which is not 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 legislators), specifying the action and resource. It distinguishes from siblings like 'get_legislator' which retrieves a single entity.

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 lists parameters with examples but does not explicitly state when to use this tool versus alternatives like 'get_legislator'. No when-not-to-use or context cues are provided.

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