［NEW遊戲發售預告片揪團交換］用 Wikidata 公開資料查任何遊戲的發售日、平台、開發商、官方網站與 YouTube 影片。
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": "games__lookup_any_game"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes |
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 burden. It usefully discloses the data source ('Wikidata 公開資料'), implying a free, read-only, possibly incomplete dataset, which is meaningful behavioral context. It says nothing about ambiguous-name handling, not-found behavior, or coverage limits.
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?
Essentially one sentence, which is appropriately short, but it is front-loaded with the noisy bracketed tag '［NEW遊戲發售預告片揪團交換］' that does not earn its place. The useful content (source, returned fields) is buried behind it.
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?
For a one-parameter lookup with no output schema, listing the returned fields is helpful and roughly complete at the value level. However, with no annotations and no parameter documentation, an agent still lacks the minimum needed to know what to pass and when this tool beats its 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?
The single parameter 'q' has 0% schema description coverage, and the description never explains what to pass. It only implies via '查任何遊戲' that the input is a game name, leaving format (Chinese vs English title, Wikidata QID, aliases) undefined.
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?
States a specific verb (查/look up) and resource (任何遊戲/any game) plus the concrete fields returned: release date, platforms, developer, official site, YouTube videos. This distinguishes it as a broad name-based lookup, though it never explicitly contrasts with games__get_game or games__list_games, so sibling differentiation is left to inference.
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?
There is no when-to-use guidance, no prerequisite, and no named alternative. The agent must guess whether to call this versus games__get_game or games__release_calendar. The bracketed promotional prefix adds no routing information.
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.