GAMES.GG

Discover games

discover_games

Read-onlyIdempotent

Use for what should I play, game recommendations, best or top rated games, popular or trending games, most anticipated upcoming games, which games are gaining attention, or why one game is popular. Filters by genre, platform, free to play and release status only. It does not know the user's library, preferences, hardware or play history. Returns games with their evidence, source and GAMES.GG url, and the signals used. Signals have separate evidence and sources, with no combined score. Rank and hype counts are not growth measurements. Always pass the user's language in locale; pt maps to pt-BR.

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": "discover_games"
  }
}

Input Schema

Name	Required	Description
`game`	No	One game title or slug: explain its signals instead of listing games.
`genre`	No	Genre slug, e.g. rpg, shooter, strategy, survival or co-op.
`limit`	No	Default 5.
`locale`	No	Always pass the user's language as a site locale, e.g. pt or pt-BR, es, fr; default en.
`period`	No	popular window: last 7 days (default) or last 90 days.
`signal`	No	editorial (default): best GAMES.GG review ratings, for what to play. popular: GAMES.GG reader attention ranking. anticipated: upcoming releases by editor pins and IGDB hype. growth: games gaining attention between two periods.
`status`	No	Release status; playable means out and playable now.
`platform`	No	Platform slug, e.g. windows (PC), playstation, xbox, nintendo-switch, ios, android or web.
`freeToPlay`	No

Output Schema

Name	Required	Description	Default
`games`	Yes
`hubUrl`	No
`locale`	Yes
`signals`	Yes
`suggestions`	Yes
`unsupported`	No
`clarification`	No
`localeFallback`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive. The description adds real value beyond them: returned fields (evidence, source, GAMES.GG url, signals), the caveat that signals have separate evidence with no combined score, and that rank/hype counts are not growth measurements. That is a strong disclosure, though pagination/limit interaction is left to the schema.

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?

Front-loaded with use cases and then constraints, with no filler sentences. It is somewhat dense and runs long as continuous prose, which slightly hurts scannability, but each clause carries information.

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

Completeness5/5

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

For a 9-param read-only discovery tool with an output schema, the description covers when to use, scope limits, return contents and signal interpretation. Nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (89%), so baseline is 3, but the description adds meaning: locale must always be passed and pt maps to pt-BR, and the game parameter is for explaining one title's signals rather than listing. These facts are not fully conveyed by the schema alone.

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?

States specific intents (recommendations, top rated, trending, upcoming, why a game is popular) and the resource is clearly games, which separates it from siblings like find_game and my_games. The phrase 'Filters by genre, platform, free to play and release status only' further pins down its scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit list of when to use it ('what should I play', recommendations, trending, anticipated), then gives exclusions: it does not know the user's library, preferences, hardware or play history, which steers an agent toward my_games or find_game for those needs.

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

All GAMES.GG tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?