isthereanydeal-mcp

games_info_v2

Retrieve game details (title, pricing, availability) by game ID. Supports price comparison and collection management by providing accurate game information.

Instructions

[GET] /games/info/v2 - Game Info。必填: query: id。需要 API Key（环境变量: ITAD_API_KEY, ISTHEREANYDEAL_API_KEY, APIKEY, apikey）。可读取资源 itad://guide/calling 获取完整调用说明。

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": {
      "query": "<query>"
    },
    "name": "games_info_v2"
  }
}

Input Schema

Name	Required	Description
`body`	No	请求体（可选）
`query`	Yes	Query 参数对象，必填: id
`headers`	No	请求头对象（可选）
`oauthToken`	No	OAuth token（非 oauth 接口可忽略）
`pathParams`	No	路径参数对象（可选）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

C2.6/5.0

Behavior3/5

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

The description discloses that an API key is required (listing environment variables) and points to a resource for full call instructions. However, it does not describe the return format, error behavior, rate limits, or side effects. Given no annotations, this is minimal but useful context.

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 description is brief and front-loaded with the endpoint and required information. The env var list is somewhat verbose but serves a practical purpose. No wasted sentences; it is appropriately sized for the tool's simplicity.

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?

The tool has no output schema and no description of return values, making it incomplete for an agent to know what to expect. It also lacks any differentiation from sibling tools. The pointer to the guide resource is helpful but does not compensate for missing core behavioral context.

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 coverage is 100%, so the baseline is 3. The description repeats that 'query: id' is required, which is already in the schema, but adds no meaning about what 'id' represents or how it is used. The API key requirement is not a parameter, so it does not enhance parameter semantics.

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

Purpose2/5

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

The description 'Game Info' essentially restates the tool name 'games_info_v2' without specifying what information is returned or the action performed. It lacks a clear verb and does not distinguish itself from sibling tools like games_prices_v3 or games_overview_v2.

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?

No guidance is provided on when to use this tool versus alternatives. It mentions required id and API key, but does not state the scenario or context for preferred use, nor does it name any alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server