Skip to main content
Glama

台灣運動賽事日程

列出台灣關注的 2026–2028 運動賽事

list_sports_events
Read-onlyIdempotent

列出台灣關注的 2026–2028 運動賽事(中職、MLB、NBA、TPBL、亞運、世界 12 強、奧運等),含日期、地點、狀態、台灣轉播;可依項目、狀態、日期篩選。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sports_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
sportNo
statusNo
taiwanNo只看有中華隊或台灣相關資訊的賽事

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the returned fields (日期、地點、狀態、台灣轉播) and the bounded 2026–2028 coverage window. It still says nothing about result volume, pagination, or how the open-world dataset is sourced, so it goes only modestly beyond the annotations.

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?

A single front-loaded sentence with the scope first, then returned fields, then filterability — a logical order with no filler. The parenthetical league list is long but earns its place by clarifying coverage.

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?

With no output schema, the description carries the burden of describing return values and does so at a high level (date, location, status, Taiwan broadcast). For a 5-parameter, zero-required listing tool this is close to sufficient, with only result-size and date-format details missing.

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?

Schema coverage is only 20% (only taiwan is documented), so the description must compensate, and it largely does: 項目 maps to sport, 狀態 to status, and 日期 to the from/to pair, while the league examples clarify the sport enum's intent. It does not specify date string format or whether from/to bounds are inclusive, leaving a residual gap.

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?

States a specific verb (列出) plus resource (運動賽事) and narrows scope to Taiwan-relevant events in 2026–2028, with concrete league examples (中職、MLB、NBA、TPBL、亞運、世界 12 強、奧運). It reads clearly as a bulk-listing tool, though it never names a sibling such as get_sports_event or sports_calendar to draw the boundary explicitly.

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?

The clause 可依項目、狀態、日期篩選 implies how to narrow results, which is genuine usage guidance. However, there is no statement of when to prefer this over the single-event lookup or calendar siblings, and no exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.