get_gameGet full details for a single video game: description, ratings, Metacritic score, platforms, genres, developers, publishers, ESRB rating, and playtime. Example: get_game({ id: "the-witcher-3-wild-hunt" })
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | RAWG game id or slug, e.g. "3328" or "the-witcher-3-wild-hunt" | |
| _apiKey | No | Optional — your own RAWG API key for higher limits; omit to use the shared Pipeworx key. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "id": "the-witcher-3-wild-hunt"
+ },
+ {
+ "id": "3328"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint, idempotentHint, destructiveHint) already declare safety. The description adds value by listing the specific fields returned (description, ratings, Metacritic score, etc.) and providing an example, but does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loads the purpose, and includes an example. Every sentence is useful and concise with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the annotations cover safety and idempotency, and the schema covers parameters, the description adds the list of return fields and an example. No output schema exists, but the description compensates adequately. However, it could mention expected data size or rate limits.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters. The description's example adds a concrete id value but does not add meaning beyond the schema's description of the id parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'Get' and resource 'single video game', lists fields (description, ratings, Metacritic score, etc.), and provides an example. This clearly distinguishes it from sibling tools like search_games.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use for retrieving full details of a single game but does not explicitly state when to use this tool over siblings (e.g., search_games). No when-not or alternative guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools have unclear boundaries: ask_pipeworx_beta is explicitly identical to ask_pipeworx, bet_research overlaps heavily with polymarket_edges, and entity_profile/recent_changes/compare_entities/validate_claim all pull from the same SEC/news fundamentals space. The memory trio and game lookup tools are distinct, but too many other tools could be confused for one another.
The surface is uniformly snake_case and has some strong families (list_*, polymarket_*, ask_pipeworx_*), but it mixes verb-led names (search_games, remember, validate_claim) with noun-led names (entity_profile, polymarket_arbitrage, pipeworx_trending) and brand-style names like ask_pipeworx. There is a pattern, but it is not a single consistent one.
35 tools is a heavy surface, and the set feels sprawling rather than focused: a four-tool RAWG game submodule sits alongside a general-purpose research platform, Polymarket edge tooling, memory helpers, subscriptions, feedback, and meta-utilities. Many of these could have been consolidated or split into separate servers.
As a general data-research and prediction-market platform the coverage is strong, with lookup, grounded verification, entity resolution, research fan-out, and subscription flows. But for a server named Rawg, the game domain is thinly covered with only search/get/list tools and no game-detail enrichment or broader browsing surface, leaving the core domain feeling like an afterthought.