GAMES.GG

Find a game

find_game

Read-onlyIdempotent

Look up a video game by name. Use it for a game's release date, platforms or cover, and to resolve a game name before search_guides or search_editorial. Pass only the game title as query. Returns matching games, each with slug, name, platforms, releaseDate, cover and its GAMES.GG page url. Always pass the user's language in locale; pt maps to pt-BR.

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

Input Schema

Name	Required	Description	Default
`query`	Yes
`locale`	No	Always pass the user's language as a site locale, e.g. pt or pt-BR, es, fr; default en.

Output Schema

Name	Required	Description	Default
`games`	Yes
`locale`	Yes
`localeFallback`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavior beyond that: it returns multiple matching games (fuzzy lookup, not exact resolution) and encodes a locale normalization rule (pt maps to pt-BR). It omits result limits or ranking behavior, which would have pushed it higher.

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?

Four short sentences, front-loaded with purpose and use cases before parameter rules. The sentence enumerating return fields (slug, name, platforms, releaseDate, cover, url) is somewhat redundant given an output schema exists, but it is brief and not disruptive.

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 two-parameter, read-only lookup with an output schema, the description covers purpose, usage, downstream steps, query constraints and locale behavior. Nothing essential is missing; only edge details like pagination or match-ranking are absent.

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 only 50%, and the description compensates for the undocumented query parameter by clarifying it must be only the game title, not an ID or URL. The locale guidance largely repeats the schema's own locale description, so it adds little new there, but the query constraint is meaningful and not derivable from the schema.

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 a specific verb and resource ('Look up a video game by name') and immediately scopes the use cases: release date, platforms, cover, and name resolution. It is clearly distinguishable from siblings like search_guides or discover_games because it is a title-to-entity lookup rather than a content search.

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

Usage Guidelines4/5

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

Gives explicit when-to-use conditions ('for a game's release date, platforms or cover') and positions itself as a prerequisite step before search_guides or search_editorial. It does not explicitly state when-not to use it versus discover_games or get_calendar, so it falls short of a full routing guide.

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?