Skip to main content
Glama
narumiruna

Taiwan Legislative Yuan MCP Server

get_ivod

Retrieve detailed information for a specific legislative committee meeting video, including playback URL, transcript, and speech timing, by providing the IVOD identifier.

Instructions

取得特定 IVOD(網路電視)影片的詳細資訊。

Args:
    ivod_id: IVOD 編號,必填,例:156045

Returns:
    str: JSON 格式,包含 IVOD 影片詳細資訊,包括播放頁面網址、影片網址、
         會議資料、影片長度、委員發言時間、逐字稿等。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ivod_idYesIVOD 編號,必填,例:156045

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It mentions the return format (JSON string) and that errors return Chinese error messages. It does not disclose read-only nature, auth requirements, or behavior for missing IVOD. Adequate but not exhaustive.

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?

Description is concise, using a single sentence for purpose and structured Args/Returns/Raises sections. No fluff, but could be even shorter. Slightly more verbose than necessary.

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?

Given that an output schema exists (though not shown), the description adequately explains return content. It covers parameters and error behavior. However, it lacks details on edge cases or prerequisites for a simple get tool.

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 the parameter 'ivod_id' is already described in the schema. The description repeats the same info in the Args section, adding no new meaning beyond the schema. Baseline score of 3.

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?

Description clearly states it retrieves detailed info for a specific IVOD video, using the verb '取得' and specifying the resource 'IVOD影片詳細資訊'. It distinguishes from sibling tools like list_ivods and get_meet_ivods by being the specific get-by-ID variant.

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?

Description does not explicitly guide when to use this tool vs alternatives. It only describes what it does; there is no mention of when to prefer this over list_ivods or get_meet_ivods. Usage is implied but not stated.

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