Skip to main content
Glama

AI 代理人任務中樞

依月份列出各賽事的開幕、決賽與關鍵日期

sports__sports_calendar
Read-onlyIdempotent

[台灣運動賽事日程資料庫]依月份列出各賽事的開幕、決賽與關鍵日期。

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__sports_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuine piece of context: the data source is the Taiwan sports-event calendar database (台灣運動賽事日程資料庫), which bounds the coverage domain. However, it says nothing about what happens when month is omitted (the parameter is optional, with 0 required), and nothing about result shape or ordering.

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 short sentence, front-loaded with a bracketed source tag followed by the action and scope. It is efficient with no filler, though the content is almost entirely a restatement of the title, so the sentence earns less than its brevity suggests.

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?

For a one-parameter read-only tool with an optional argument, full schema coverage and rich annotations, the definition is adequate but leaves two agent-relevant questions open: the behavior when month is not supplied, and the nature/ordering of returned dates (no output schema exists to fill that gap). It is minimally sufficient rather than complete.

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 description coverage is 100%, with the single parameter month already documented as 'YYYY-MM', so the schema carries the format burden. The description reinforces the monthly grouping but adds no new meaning: it does not say whether an absent month defaults to the current month or returns all months. Baseline 3 applies when the schema does the heavy lifting.

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 a concrete verb and resource: list (列出) each event's opening, finals and key dates, grouped by month. That is more specific than the bare name 'sports_calendar' and roughly distinguishes it from siblings like list_sports_events or get_sports_event. It stops short of naming any alternative, and the wording largely mirrors the title, so it does not fully separate itself from the other sports 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?

There is no when-to-use guidance at all: nothing explains when an agent should pick this month-oriented calendar over list_sports_events, whats_on, or event_countdown. Use is only implied by the word 依月份. No prerequisites, no exclusions, no alternative routing.

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.