Skip to main content
Glama
Sign In
yagames-mcp

yagames-mcp

by PETERGS27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

yagames-popular

Retrieve popular games from Yandex Games catalog, optionally filtered by category slug.

Instructions

Get popular games from Yandex Games catalog, optionally filtered by category

Tool call template

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

Input Schema

NameRequiredDescriptionDefault
categoryNoCategory slug (e.g. casual, puzzles, match3, merge, action). See yagames-categories for full list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the behavioral transparency burden. 'Get' clearly conveys a read-only catalog lookup, but the description omits useful behavioral details such as pagination, result limits, ordering, or error behavior for invalid categories.

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 compact sentence that front-loads the main operation and then adds the one relevant filter caveat. Every word contributes meaning, with no filler or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description is largely sufficient for correct invocation. The only notable gap is the lack of information about the return format, result count, or pagination behavior.

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%, so the single optional category parameter is already well documented with examples and a pointer to yagames-categories. The description adds only the word 'optionally,' which is also implied by the schema having zero required parameters.

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?

States the specific operation 'Get popular games' and names the resource, the Yandex Games catalog, with an optional category filter. This is clear and distinct from the search and categories siblings, though it does not explicitly name those alternatives.

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 when to use this tool—when popular games are wanted—and the category schema points to yagames-categories for valid values. However, it gives no explicit guidance on when to choose this over yagames-search or other catalog-related tools.

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

Deploy Server

Other Tools