［NEW遊戲發售預告片揪團交換］列出 2026–2027 重點遊戲（PS5、Xbox、PC、Switch 2、手機），含公開日、發售日、狀態；可依平台、狀態、日期篩選。
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": "games__list_games"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ||
| from | No | ||
| status | No | ||
| platform | No | ||
| upcoming | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the returned data categories (公開日, 發售日, 狀態) which is useful given the missing output schema, but it says nothing about read-only safety, result limits, pagination, or how 'to/from' defaults behave.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core sentence is a single efficient line covering scope, fields, and filters. However, the bracketed prefix ［NEW遊戲發售預告片揪團交換］ is promotional noise unrelated to this list operation (it references trailer/group-buy exchange), diluting the front-loaded signal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 5 parameters, 0% schema coverage, no annotations, and no output schema, the description should do more. It covers purpose and some filters but omits the meaning of 'upcoming', the from/to date semantics, result caps, and any routing guidance among the many overlapping games__ siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% across 5 parameters, so the description must compensate. It maps platform and status filters and loosely implies a date filter (日期), but the 'to', 'from', and especially the boolean 'upcoming' parameters are never explained, and the from/to directionality and format are left ambiguous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb (列出/list) plus resource (2026–2027 重點遊戲) and enumerates the platforms and fields covered, so an agent immediately knows what it returns. It stops short of distinguishing itself from near-siblings such as games__release_calendar or games__lookup_any_game, which overlap heavily with a filtered game listing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states the available filters (platform, status, date) but never says when to choose this tool over games__get_game, games__lookup_any_game, or games__release_calendar. There is no when-to-use, when-not-to-use, or alternative routing, leaving selection to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.