Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_law_versions

List versions of Taiwan laws filtered by number, date, action, or proposer. Returns paginated JSON results with customizable fields.

Instructions

列出法律版本資料。

Args:
    law_number: 法律編號,例:90481
    version_number: 版本編號,例:90481:1944-02-29-制定
    date: 日期,格式:YYYY-MM-DD,例:1944-02-29
    action: 動作,例:制定
    main_proposer: 歷程主提案,例:張子揚
    progress: 歷程進度,例:一讀
    current_version: 現行版本,現行或非現行
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式,包含法律版本列表。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
law_numberNo法律編號,例:90481
version_numberNo版本編號,例:90481:1944-02-29-制定
dateNo日期,格式:YYYY-MM-DD,例:1944-02-29
actionNo動作,例:制定
main_proposerNo歷程主提案,例:張子揚
progressNo歷程進度,例:一讀
current_versionNo現行版本,現行或非現行
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?

With no annotations, the description carries the full burden. It specifies the return type (JSON string) and error handling (Chinese error messages). Pagination behavior is implied via 'page' and 'limit' parameters. However, it does not explicitly state that the operation is read-only, nor does it disclose any rate limits or performance characteristics.

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 clear sections for Args, Returns, and Raises. It is appropriately detailed without unnecessary verbosity. Each parameter gets a line with an example, keeping it organized.

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 tool has 10 parameters, all optional, and an output schema is present, the description adequately covers input details, return type, and error handling. It is complete for an agent to understand how to invoke the tool, though it could list possible values for 'action' or 'progress'.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by providing concrete examples for each parameter (e.g., law_number: 90481, date: 1944-02-29), which clarifies format and usage beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states '列出法律版本資料' (list legal version data), indicating a list operation. It enumerates filtering parameters, which distinguishes it from siblings like 'get_law_versions' that might retrieve a single version. However, it does not explicitly contrast with the similarly named sibling 'get_law_versions'.

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 is provided on when to use this tool versus alternatives (e.g., 'get_law_versions', 'get_law_version'). There is no mention of prerequisites, typical use cases, or scenarios where other tools would be more appropriate.

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