Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_law_versions

Retrieve historical version records of any law by providing its law ID, with optional filters for date, action, or proposer.

Instructions

取得特定法律過往的版本紀錄列表。

Args:
    law_id: 法律編號,必填,例:09200015
    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_idYes法律編號,必填,例:09200015
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
Behavior2/5

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

No annotations are provided, yet the description does not disclose whether the operation is read-only, destructive, or requires specific permissions. It mentions returning JSON and error messages, but lacks details on side effects, rate limits, or postconditions.

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

Conciseness3/5

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

The description is moderately sized but includes a verbose Args section that duplicates schema details. It could be streamlined by focusing on usage intent and omitting redundant parameter lists.

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

Completeness3/5

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

Given the tool has 11 parameters and an output schema, the description provides basic return format and error handling. However, it lacks details on sorting, default ordering, or pagination behavior beyond parameter defaults, leaving gaps for complete understanding.

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 the baseline is 3. The description's Args section largely repeats parameter descriptions, adding minimal value beyond stating '必填' for law_id. It does not enhance understanding of parameter behavior.

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 it retrieves a list of historical version records for a specific law ('取得特定法律過往的版本紀錄列表'). Among sibling tools like 'get_law' (detail) and 'get_law_version' (single version), this tool's purpose is distinct.

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 listing historical versions but does not explicitly state when to use this tool versus alternatives like 'list_law_versions' or 'get_law_version'. No when-not-to-use or contextual guidance is 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