Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

by narumiruna

get_gazette_agendas

List the agenda entries of a specific Legislative Yuan gazette using its gazette ID. Apply filters like meeting date, volume, issue, or term to refine the results.

Instructions

取得特定公報所含的公報目錄列表。

Args:
    gazette_id: 路徑中的公報編號,必填,例:1137701
    gazette_number: 查詢條件中的公報編號,例:1137701
    volume: 卷,例:113
    issue: 期,例:77
    booklet: 冊別,例:1
    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
pageNo頁數,預設1
termNo屆,例:11
issueNo期,例:77
limitNo每頁筆數,預設20,建議不超過100
volumeNo卷,例:113
bookletNo冊別,例:1
gazette_idYes路徑中的公報編號,必填,例:1137701
meeting_dateNo會議日期,格式:YYYY-MM-DD,例:2024-10-04
output_fieldsNo自訂回傳欄位(如需指定欄位,請填寫欄位名稱列表)
gazette_numberNo查詢條件中的公報編號,例:1137701

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations are provided, and the description does not mention any side effects, rate limits, authentication, or safety considerations. It is a read operation but not explicitly stated.

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

Conciseness5/5

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

The description is concise and well-structured, including args, returns, and raises sections. It is not verbose and gets to the point.

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?

Provides return type (string containing JSON) and error handling (Chinese error message), but lacks details on the structure of the returned agenda list. Given the simplicity, it is partially complete.

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?

All parameters are described with concrete examples (e.g., gazette_id: 1137701, meeting_date format). The descriptions add useful context beyond the schema, though they largely mirror the schema.

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 the tool retrieves the list of agendas for a specific gazette, using a specific verb and resource. It distinguishes from the generic list_gazette_agendas by specifying the gazette_id.

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. It relies on the parameter requirement of gazette_id, but does not mention conditions or when to prefer this over similar tools.

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