Skip to main content
Glama

Get game details

get_game_details
Read-onlyIdempotent

Return the authoritative public catalog record for one game id from search_games: every fact with its evidence method, source and date (or "unknown"), developer attribution, link status and play URL, plus related: up to 8 similar games (shared genre, sub-genre, style, theme and tone, later also what the same people play), each with the reasons.

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": {
      "id": "<id>"
    },
    "name": "get_game_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGame id from search_games results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and closed-world, so the safety profile is covered; the description earns credit for disclosing the payload shape beyond annotations: per-fact evidence method, source, date-or-'unknown', developer attribution, link status, play URL, and a capped set of up to 8 related games with reasons. It does not cover failure behavior for a missing id, which is the remaining gap.

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?

One sentence, front-loaded with the purpose and then enumerating the returned contents in a logical order; nearly every clause carries information an agent cannot get from structured fields. The trailing parenthetical 'later also what the same people play' is vague and slightly blurs an otherwise tight enumeration.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, including the evidence/source/date framing and the related-games cap. Combined with annotations covering safety, the only omission is what happens on an unknown or malformed id.

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?

Only one parameter, and the schema already documents it at 100% coverage ('Game id from search_games results'), including the pattern constraint. The description's 'one game id from search_games' restates the same provenance without adding format or edge-case meaning, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb ('Return') and a precisely scoped resource ('the authoritative public catalog record for one game id'), and ties the id's origin to search_games, so the agent can tell this apart from the search sibling. It stops short of an explicit 'use search_games to find ids, use this to expand one' routing statement, which keeps it just below a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'one game id from search_games' signals the prerequisite (you must have an id from search results first) but never states when to call this versus search_games, nor what to do when the id is unknown or invalid. Adequate but leaves the agent to infer the workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources