Skip to main content
Glama

AI 代理人任務中樞

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

sports__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": "sports__list_sports_events"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 beyond that: the dataset's temporal boundary (2026–2028), the league coverage, and the fact that each record carries date, venue, status and Taiwan broadcast info. It omits result volume/pagination or default behavior when no filter is supplied.

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?

One dense sentence, front-loaded with a bracketed source tag and the verb, then examples, then filter capability — the ordering an agent can scan quickly. The parenthetical league list is long but earns its place by disambiguating scope; nothing is redundant.

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?

With no output schema, the description usefully enumerates the record fields, which is the main gap it needs to fill. However, for a 5-parameter list tool with all-optional params, it never says what happens when called with no filters (all events? a capped page?) or how results are ordered/limited.

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 description coverage is only 20% (only the taiwan flag is documented), so the description must compensate — and it largely does by naming the three filter axes: 項目 (sport), 狀態 (status), 日期 (from/to). The enumerated sport and status values are visible in the schema enums, so no extra work is needed there. What's missing is the date format/range semantics for from/to and mention of the taiwan flag.

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 opens with a specific verb + resource ("列出…運動賽事") and pins down scope tightly: Taiwan-relevant events in 2026–2028, with named leagues (CPBL, MLB, NBA, TPBL, Asian Games, Premier12, Olympics). It also enumerates the return fields, so the agent knows what a result set looks like. It does not name a sibling such as sports__sports_calendar or sports__whats_on, so it stops short of a 5.

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?

"可依項目、狀態、日期篩選" implies when to use the filters but never states the selection rule versus alternatives (e.g., use get_sports_event for a single event, sports_calendar for a full calendar). There are no explicit exclusions or prerequisites, leaving the agent to infer routing from sibling names alone.

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.