Skip to main content
Glama

台灣運動賽事日程

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

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

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 nothing beyond that: it does not say which events/competitions are in scope, whether results are grouped or sorted, or what happens when month is omitted (no required parameters).

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 short sentence with no filler and an immediately front-loaded scope, so nothing is wasted. Its terseness is a weakness in coverage rather than verbosity, which other dimensions capture.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 would need to convey what a returned calendar entry looks like, and it does not. It also leaves the default behavior of the optional month parameter unspecified, which is the main practical ambiguity for this 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 description coverage is 100% and the single month parameter already documents its YYYY-MM format, so the baseline of 3 applies. The description repeats the month grouping idea but adds no convention details such as timezone, boundary handling, or range limits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names a specific resource (各賽事的開幕、決賽與關鍵日期) and a grouping (依月份), so an agent can tell it produces a per-month calendar of key dates rather than a single event lookup. However, it is a verbatim copy of the title and gives no hint of how it differs from siblings such as list_sports_events, whats_on, or event_countdown.

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 or when-not-to-use guidance at all — nothing says to prefer this over list_sports_events for a full listing or over event_countdown for a single event's next milestone. The agent must infer the choice purely from the tool name.

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.