GAMES.GG

Save a guide

save_guide

Idempotent

Use when the user asks to save, bookmark or read later a guide on their GAMES.GG account. guide is the guideSlug from search_guides, or the guide value from my_saved_guides or my_code_follows; pass the search result's locale. Returns what changed and the guide's GAMES.GG url.

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": {
      "guide": "<guide>"
    },
    "name": "save_guide"
  }
}

Input Schema

Name	Required	Description	Default
`guide`	Yes	The guideSlug from search_guides, or the guide value from my_saved_guides or my_code_follows.
`locale`	No	The locale of that search_guides result.

Output Schema

Name	Required	Description
`url`	Yes
`saved`	Yes
`title`	Yes
`changed`	Yes	false when the account already had this state.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already disclose that this is a non-destructive, idempotent write operation and not open-world. The description adds account context and says it returns what changed plus the guide URL, which gives useful behavioral context beyond the annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three tight sentences with the usage trigger front-loaded, followed by parameter sourcing and return information. Every sentence contributes directly to correct invocation.

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 write tool with full schema coverage, rich annotations, and an output schema, the description covers the key usage and data-source context. It does not discuss permission or authentication edge cases, but the account mention and annotations cover the main behavioral concerns.

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

Parameters3/5

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

Schema description coverage is 100%, so both guide and locale are already documented. The description restates the guide source and locale usage from the schema but adds no extra syntax, formatting, or edge-case meaning beyond that baseline.

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 states a specific verb and resource: saving, bookmarking, or reading later a guide on a GAMES.GG account. This clearly distinguishes it from save_game and from unsave_guide by resource and direction of operation.

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?

It gives an explicit trigger: use when the user asks to save, bookmark, or read later a guide. It does not explicitly name alternatives or exclusions, but the trigger is clear enough for an agent to select this tool over siblings in most cases.

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?