gamedeals

Get Game Details

get_game_details

Read-onlyIdempotent

Get complete pricing history for a game: current deals across all stores, historical low prices, and price trends over time.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	CheapShark game ID (obtained from search_games)

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Full game name
`deals`	Yes
`thumb`	Yes	Thumbnail image URL
`game_id`	Yes	CheapShark game ID
`steam_app_id`	Yes	Steam app ID or null if not on Steam
`cheapest_price_ever`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cheapest_price_ever": {
+      "properties": {
+        "date": {
+          "description": "ISO date (YYYY-MM-DD) of lowest price",
+          "type": "string"
+        },
+        "price": {
+          "description": "Lowest price ever recorded in USD",
+          "type": "number"
+        }
+      },
+      "required": [
+        "price",
+        "date"
+      ],
+      "type": "object"
+    },
+    "deals": {
+      "items": {
+        "properties": {
+          "deal_id": {
+            "description": "Unique deal identifier",
+            "type": "string"
+          },
+          "price": {
+            "description": "Current price in USD",
+            "type": "number"
+          },
+          "retail_price": {
+            "description": "Retail/MSRP price in USD",
+            "type": "number"
+          },
+          "savings_percent": {
+            "description": "Discount percentage",
+            "type": "number"
+          },
+          "store_id": {
+            "description": "Store ID",
+            "type": "string"
+          }
+        },
+        "required": [
+          "store_id",
+          "deal_id",
+          "price",
+          "retail_price",
+          "savings_percent"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "game_id": {
+      "description": "CheapShark game ID",
+      "type": "string"
+    },
+    "name": {
+      "description": "Full game name",
+      "type": "string"
+    },
+    "steam_app_id": {
+      "description": "Steam app ID or null if not on Steam",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "thumb": {
+      "description": "Thumbnail image URL",
+      "type": "string"
+    }
+  },
+  "required": [
+    "game_id",
+    "name",
+    "steam_app_id",
+    "thumb",
+    "cheapest_price_ever",
+    "deals"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "id": "612834"
+  }
+]
```
First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description only needs to add behavioral context. It does so by specifying the exact output scope: current deals across stores, historical lows, and price trends. This goes 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 a single, well-structured sentence that leads with the action and then provides detail after a colon. Every word serves a purpose, making it highly concise without losing clarity.

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

Completeness5/5

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

Given one clearly documented parameter, comprehensive annotations, and existing output schema, the description is complete for an agent to understand what the tool does and when to invoke it. No additional explanation of return values is needed because the output schema covers that.

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?

The input schema already has a full description for the single 'id' parameter (CheapShark game ID from search_games), achieving 100% schema coverage. The tool description adds no additional parameter-level meaning, so the baseline of 3 applies.

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 uses the specific verb 'Get' and clearly identifies the resource: complete pricing history for a game. It enumerates the three component data types (current deals, historical lows, price trends), distinguishing it from siblings like search_games (which finds game IDs) and search_deals (which searches deals).

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?

The description implies usage by stating its purpose—retrieving comprehensive pricing for a single game—but does not explicitly exclude alternatives like search_deals. The schema description notes the ID is obtained from search_games, which hints at the appropriate flow, but an explicit when-to-use would be stronger.

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

All gamedeals tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.