Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_law_contents

Retrieve law articles and their contents from Taiwan's Legislative Yuan by specifying law number, version, article number, or other filters to view current or historical versions.

Instructions

列出法條資料。

Args:
    law_number: 法律編號,例:90481
    version_id: 版本編號,例:90481:90481:1944-02-29-制定:1
    order: 順序,例:1
    article_number: 條號,例:第一條
    current_version_status: 現行版,可選值:現行、非現行
    version_tracking: 版本追蹤,例:new
    page: 頁數,預設1
    limit: 每頁筆數,預設20
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的法條列表。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
law_numberNo法律編號,例:90481
version_idNo版本編號,例:90481:90481:1944-02-29-制定:1
orderNo順序,例:1
article_numberNo條號,例:第一條
current_version_statusNo現行版,可選值:現行、非現行
version_trackingNo版本追蹤,例:new
pageNo頁數,預設1
limitNo每頁筆數,預設20
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 provided. The description mentions return type (JSON string) and error handling (Chinese error messages), but does not disclose read-only nature, idempotency, or potential side effects. For a listing tool with no annotations, more behavioral context is expected.

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 a clear purpose line followed by parameter definitions. It is reasonably concise but could be more compact by removing verbatim repeats of schema descriptions.

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?

The description covers return type and error handling, and an output schema exists. However, it lacks explanation of parameter dependencies (e.g., whether law_number or version_id is needed) and constraints.

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's parameter list essentially duplicates the schema's descriptions without adding new meaning or relationships.

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 states '列出法條資料' (list law article data), which clearly indicates a listing operation. The name 'list_law_contents' and the parameter list (filters, pagination) reinforce this. However, it does not explicitly differentiate from sibling tools like get_law_content, though inference is possible.

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 explicit guidance on when to use this tool versus alternatives. The description simply lists parameters without explaining scenarios or prerequisites.

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