Skip to main content
Glama

查單一賽事

sports__get_sports_event
Read-onlyIdempotent

[台灣運動賽事日程資料庫]查單一賽事:日期、地點、主辦、重要日期、中華隊資訊、台灣轉播平台與來源;中文或英文名稱皆可(如 世界12強、台灣大賽、TPBL、LA28)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "sports__get_sports_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds what the response contains and that the tool queries a Taiwan sports-event calendar, but it says nothing about behavior on ambiguous or partial names (single best match vs. multiple candidates) or on no match, which is the main uncertainty for an open-world name lookup.

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?

The definition is a single front-loaded sentence that moves from database context, to the verb, to the returned fields, to the input-language rule. The semicolon-separated field list is dense but every clause carries information; no sentence is wasted.

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?

There is no output schema, so the description has to cover return values, and the field enumeration does that. However, for an open-world name lookup with a single free-text parameter it should also say what happens when the name matches nothing or matches several events, and it does not.

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 0% and the schema says only that 'q' is a string, so the description must carry the meaning, and it does: q accepts either Chinese or English event names, with concrete examples (世界12強, 台灣大賽, TPBL, LA28). It stops short of specifying matching rules (exact vs. substring, alias handling).

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 pairs a specific verb with its resource, 查單一賽事 ('get a single sports event'), and then lists the fields returned (date, venue, organizer, key dates, Chinese-team info, Taiwan broadcast platforms, source), so the agent knows exactly what retrieval this tool performs. Its scope is not distinguished in words from siblings such as lookup_any_sports_event or list_sports_events; '單一' helps, but the agent still has to guess why it should choose this tool over those.

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?

Usage is implied: the agent should call this tool when it needs details for one already-identified event. The definition offers input-level guidance that Chinese and English names both work, with four examples, but it never states when to use this tool instead of a listing tool, nor which alternative to use for fuzzy or multi-event discovery.

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.

Resources