GAMES.GG

Read a review or article

read_editorial

Read-onlyIdempotent

Read a GAMES.GG review or article found with search_editorial. Pass the type and slug of that item; pass section, an anchor from tableOfContents, to read one section. Returns the verdict with pros and cons, an opening excerpt or the section, and tableOfContents. Includes the source URL, author and review score out of 10. 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": {
      "type": "<type>",
      "slug": "<slug>"
    },
    "name": "read_editorial"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes
`type`	Yes	review is a GAMES.GG game review; article is news or a feature.
`locale`	No	Always pass the user's language as a site locale, e.g. pt or pt-BR, es, fr; default en.
`section`	No	Exact section anchor, without #.

Output Schema

Name	Required	Description
`item`	Yes
`locale`	Yes
`verdict`	Yes
`sections`	Yes
`truncated`	Yes	True when text was left out; read a section for more.
`suggestions`	Yes	Natural follow-up questions the user could ask.
`localeFallback`	No
`tableOfContents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- removedInput schema / properties / slug / 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 declare readOnly/idempotent/non-destructive, so the description is free to spend its budget on payload shape: verdict with pros and cons, opening excerpt, tableOfContents, source URL, author, score out of 10. The section-vs-full-document behavior is useful added context. Minor gap: it doesn't say what happens if a slug is stale or a section anchor is not found.

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 the action, then inputs, then return shape, then the locale caveat – a sensible order with no filler sentences. Slightly dense: the return-value sentence partially duplicates what the output schema already declares.

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 four-parameter read tool with an output schema, nothing essential is missing: discovery path, calling modes, section semantics, and locale handling are all covered. The redundant return summary is harmless rather than a completeness failure.

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 75%, and the description fills part of the remaining gap by tying section to "an anchor from tableOfContents" and specifying the locale mapping rule ("pt maps to pt-BR"), which the schema only hints at with examples. Type and slug are described but mostly restate the schema's own enum description.

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?

"Read a GAMES.GG review or article" names a specific verb and resource, and the description immediately distinguishes the two content types and their slugs. It clearly separates this from search_editorial, which is framed as the discovery step that produces the arguments this tool consumes.

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?

It states the prerequisite workflow ("found with search_editorial"), the two calling modes (full item vs. single section via anchor), and an always-on requirement for locale. An agent knows exactly which inputs to supply and how to get them before calling.

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?