Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_laws

Retrieve a paginated list of Taiwan laws by law number, category, status, authority, date, and custom output fields.

Instructions

列出立法院法律列表。

Args:
    law_number: 法律編號,例:09200015
    category: 類別,母法或子法
    parent_law_number: 母法編號,例:09200
    law_status: 法律狀態,例:現行
    authority: 主管機關,例:總統府
    latest_version_date: 最新版本日期,格式:YYYY-MM-DD,例:2024-10-25
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的法律查詢結果。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
law_numberNo法律編號,例:09200015
categoryNo類別,母法或子法
parent_law_numberNo母法編號,例:09200
law_statusNo法律狀態,例:現行
authorityNo主管機關,例:總統府
latest_version_dateNo最新版本日期,格式:YYYY-MM-DD,例:2024-10-25
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, so the description carries full burden. It mentions returning a JSON string and Chinese error messages but does not disclose whether the tool is read-only, any authentication needs, rate limits, or side effects. For a listing tool, read-only behavior is implied but not explicit.

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 structured with Args, Returns, and Raises sections but is verbose due to repeating parameter descriptions. It could be more concise by summarizing or referencing the schema. The front-loading is adequate but not efficient.

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 9 parameters, 100% schema coverage, and an output schema, the description covers the basics: return type, error handling. However, it lacks usage context, pagination details, and relationship to sibling tools, leaving some gaps for an AI agent.

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?

All 9 parameters have descriptions in the schema (100% coverage). The description repeats these descriptions with examples, adding minimal value. It does not explain how parameters interact or provide further semantic guidance beyond what the schema already offers.

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 it lists laws from the Legislative Yuan. The verb '列出' (list) and resource '法律列表' (law list) define the action and output. However, it does not distinguish from siblings like list_law_versions or list_law_contents, which also list law-related data.

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 on when to use this tool versus alternatives such as get_law (for a single law) or list_law_versions (for versions). The description provides parameters but no context 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