Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

list_gazette_agendas

Retrieve a list of gazette agendas from Taiwan's Legislative Yuan by specifying gazette ID, volume, term, or meeting date. Filter results with pagination and custom fields.

Instructions

列出公報目錄列表。

Args:
    gazette_id: 公報編號,例:1137701
    volume: 卷,例:113
    term: 屆,例:11
    meeting_date: 會議日期,格式:YYYY-MM-DD,例:2024-10-04
    page: 頁數,預設1
    limit: 每頁筆數,預設20,建議不超過100
    output_fields: 自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)

Returns:
    str: JSON 格式的公報目錄查詢結果。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gazette_idNo公報編號,例:1137701
volumeNo卷,例:113
termNo屆,例:11
meeting_dateNo會議日期,格式:YYYY-MM-DD,例:2024-10-04
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 provided. Description does not disclose side effects, authentication needs, rate limits, or pagination behavior. It only mentions return type and error messages, which is minimal for a listing endpoint with no annotation coverage.

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 Args, Returns, and Raises sections, and front-loads the purpose. However, it is somewhat verbose, repeating schema content, which could be trimmed.

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?

Parameters are fully documented with examples and defaults. Output schema exists to cover return format. Missing higher-level context about what constitutes a gazette agenda and how pagination works (e.g., how to get next page). Almost complete for parameter use but lacks behavioral context.

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 coverage is 100%, and description largely repeats schema parameter descriptions. It adds examples inline (e.g., gazette_id='1137701') and the Returns/Raises section, but does not significantly enhance parameter understanding beyond schema.

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 '列出公報目錄列表' which is a clear verb+resource. It distinguishes from siblings like 'get_gazette_agenda' by being a listing function. However, it does not explicitly differentiate from other list tools.

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 vs alternatives (e.g., get_gazette_agenda, list_gazettes). The description only lists parameters without context or exclusions.

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