Skip to main content
Glama

get_game

Retrieve a game's summary, platforms, genres, developers, playtime averages, scores, plus your collection, rating, and wishlist status when signed in.

Instructions

Game details: summary, platforms, genres, developers, playtime averages, IB and critic scores, and your own collection/rating/wishlist state when signed in.

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

Input Schema

NameRequiredDescriptionDefault
fullNo
slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add one genuinely useful behavior: collection/rating/wishlist state only appears when the caller is signed in. It says nothing about what happens for an unknown slug, whether the call is read-only (implied but never stated), or rate limits. The presence of an output schema excuses it from describing the payload shape.

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

Conciseness3/5

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

It is a single tight sentence with no filler, which is good, but nearly all of its content is a list of return fields that the output schema already documents. The space would be better spent on the verb, the identifier, and the `full` flag.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values needn't be spelled out — yet the description is almost entirely return-value inventory, leaving the lookup contract and the `full` flag unexplained. For a simple two-parameter read tool this is not fatal, but the `full` ambiguity is a real gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate and does not. It never mentions `slug` as the identifier or explains what the boolean `full` (default true) toggles — an agent cannot infer from this text whether `full=false` returns a trimmed payload or something entirely different.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Game details" names a resource but supplies no verb and no object of the lookup (nothing says it fetches a single game by slug). The rest of the sentence enumerates returned fields rather than what the tool does, and nothing distinguishes it from the sibling get_game_stats, which an agent could plausibly confuse it with.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite statement, and no mention of when an agent should prefer get_game_stats or the list/collection tools instead. The only conditional offered is "when signed in" for the personal fields, which is a data-availability note rather than usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.