yagames-mcp

yagames-search

Search the Yandex Games catalog by keyword to find games for review, management, or publishing tasks.

Instructions

Search games in the Yandex Games catalog by keyword

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": "yagames-search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search keyword

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action and target; it does not disclose whether the operation is read-only, how results are returned, whether pagination or ordering applies, or whether it searches title, description, or metadata. The search behavior beyond the bare action remains opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no filler. The action and target are front-loaded, and every word contributes meaning.

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 annotations, so the description should clarify what a successful search returns and any notable behavior like empty results or limits. It does not. While the parameter side is complete, the overall description leaves important gaps for an agent deciding whether and how to use the 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%: the only parameter, 'query', is described as 'Search keyword'. The description's 'by keyword' adds no meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description states a specific verb ('Search'), a clear resource ('games in the Yandex Games catalog'), and a specific method ('by keyword'). It is immediately distinguishable from sibling tools like yagames-publish or yagames-list-my-games, so an agent can tell which operation this tool performs.

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?

The description implies this tool is for keyword-based searching, and the sibling list covers other operations, so the usage context is inferable. However, it does not explicitly state when to use this tool over alternatives or mention any exclusions or prerequisites, leaving some guidance to the agent's inference.

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

Deploy Server