GAMES.GG

Read a guide

read_guide

Read-onlyIdempotent

Read one GAMES.GG guide, or one section of it, in detail. Use when the user needs more than the sections search_guides returned. slug is a guideSlug from search_guides; section is an anchor from search_guides or from tableOfContents. Returns the markdown and sections with their GAMES.GG urls; a full guide also returns its tableOfContents. 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": {
      "slug": "<slug>"
    },
    "name": "read_guide"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes
`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	Default
`locale`	Yes
`markdown`	Yes
`sections`	Yes
`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.5/5.0

Behavior4/5

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

Annotations already establish the read-only, idempotent, open-world safety profile, and the description adds real behavioral context: what comes back (markdown plus sections with URLs, tableOfContents for full guides) and a locale normalization rule ("pt maps to pt-BR") that is not derivable from the annotations. The only shortfall is that some return detail overlaps the output schema rather than adding to it.

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 tight sentences, front-loaded with the purpose and followed by usage, parameter provenance, and return shape in a logical order. A small amount of the return-value sentence restates what the output schema already declares, which keeps it just short of maximal.

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 three-parameter read tool with an output schema, this covers purpose, selection criteria, every parameter's origin, and the shape of the result, so an agent can call it correctly. It would be fully complete only if it noted whether the locale is required or how a missing section behaves.

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 67%, and the description compensates by explaining provenance for slug (a guideSlug from search_guides) and section (an anchor, taken without #), which the schema only partially conveys. The locale guidance adds a mapping rule (pt to pt-BR) and a default (en) beyond the schema's examples.

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?

The description gives a specific verb and resource ("Read one GAMES.GG guide, or one section of it, in detail") and explicitly scopes it against search_guides, so an agent can tell the difference without opening either 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?

It states the selection condition directly: "Use when the user needs more than the sections search_guides returned." It also tells the agent where the slug and section values come from (search_guides or tableOfContents), which removes the main usage ambiguity.

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?