GAMES.GG

Search reviews and news

search_editorial

Read-onlyIdempotent

Search GAMES.GG reviews and news. Use for is this game worth playing, is it good, review score, what critics or GAMES.GG thought, and the latest gaming news GAMES.GG reported about a game or topic. query is the topic; omit it to list the latest coverage. When the question names a game, resolve it with find_game and pass its slug as game. type is review or article; omit it for both. Returns published reviews and articles with type, slug, summary, score out of 10, author, date and url. A game without a returned review has no GAMES.GG review. Review scores are out of 10; each item includes its source URL and author. 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": "search_editorial"
  }
}

Input Schema

Name	Required	Description
`game`	No	Resolved game slug.
`type`	No	Omit to search both types.
`query`	No	Topic or keywords. Omit to list the latest coverage.
`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
`game`	Yes	Catalog game the results were filtered by.
`items`	Yes
`locale`	Yes
`suggestions`	Yes	Natural follow-up questions the user could ask.
`localeFallback`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- removedInput schema / properties / game / pattern
```
Removed value: -"^[\\p{L}\\p{N}_-]+$"
```
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 cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's added value is the negative-result semantics — "a game without a returned review has no GAMES.GG review" — plus the 0-10 score scale and locale mapping. Genuinely useful behavioral context, though the returned-field list duplicates what the output schema already exposes.

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 purpose and use cases, and most sentences earn their place. Minor redundancy: the return fields are enumerated twice ("type, slug, summary, score out of 10, author, date and url" then re-stated as "Review scores are out of 10; each item includes its source URL and author").

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?

All four parameters are optional and fully documented, an output schema handles return values, and the description still adds the pieces an agent would otherwise get wrong: slug resolution, locale handling, and how to interpret an empty review result.

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 100%, so the baseline would be 3, but the description adds meaning beyond it: game must be a slug produced by find_game (a required upstream workflow the schema only hints at), and locale must always be the user's language with the explicit pt-to-pt-BR mapping.

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?

Opens with a specific verb and resource ("Search GAMES.GG reviews and news") and immediately maps it to concrete user intents ("is this game worth playing", "review score", "latest gaming news"), which separates it from read_editorial and search_guides without opening any schema.

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?

Explicit routing rules: name a game, resolve it with find_game and pass the slug; omit query to list latest coverage; omit type for both; always pass the user's language in locale. Alternative tools and the conditions that select them are named directly.

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?