gamedeals

Search Deals

search_deals

Read-onlyIdempotent

Search active game deals with optional filters by store, platform, or discount level. Returns deal title, store, sale price, normal price, savings %, Metacritic score, and deal rating.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Filter deals by game title (partial match supported)
`sort_by`	No	Sort order: "Deal Rating" (default), "Price", "Metacritic", or "Reviews"
`store_id`	No	Filter by store ID (use list_stores to get IDs)
`page_size`	No	Number of results to return (default: 10, max: 60)
`lower_price`	No	Minimum price filter
`upper_price`	No	Maximum price filter (e.g., 5 for deals under $5)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`deals`	Yes
`total`	Yes	Total number of deals returned

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": {
+    "deals": {
+      "items": {
+        "properties": {
+          "deal_id": {
+            "description": "Unique deal identifier",
+            "type": "string"
+          },
+          "deal_rating": {
+            "description": "Community deal rating score",
+            "type": "number"
+          },
+          "game_id": {
+            "description": "CheapShark game ID",
+            "type": "string"
+          },
+          "metacritic_score": {
+            "description": "Metacritic score (0-100) or null if unavailable",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "normal_price": {
+            "description": "Regular/normal price in USD",
+            "type": "number"
+          },
+          "sale_price": {
+            "description": "Current sale price in USD",
+            "type": "number"
+          },
+          "savings_percent": {
+            "description": "Discount percentage",
+            "type": "number"
+          },
+          "steam_rating_percent": {
+            "description": "Steam user rating percentage or null if unavailable",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "store_id": {
+            "description": "Store ID where deal is available",
+            "type": "string"
+          },
+          "thumb": {
+            "description": "Thumbnail image URL",
+            "type": "string"
+          },
+          "title": {
+            "description": "Game title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "game_id",
+          "deal_id",
+          "title",
+          "store_id",
+          "sale_price",
+          "normal_price",
+          "savings_percent",
+          "deal_rating",
+          "thumb"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total number of deals returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "deals"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "page_size": 20,
+    "sort_by": "Deal Rating",
+    "upper_price": 10
+  },
+  {
+    "lower_price": 20,
+    "store_id": "1",
+    "title": "Elden Ring",
+    "upper_price": 50
+  }
+]

First observedApr 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds value by specifying that results are limited to 'active' deals and by listing the exact fields returned, which is useful behavioral context beyond the annotations.

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 two sentences long, front-loaded with the core purpose, and every clause adds information. It is efficiently written with no redundant phrases.

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?

Given the good annotations, full schema coverage, and presence of an output schema, the description is largely complete. It covers the core functionality and return values. The only minor gap is the inconsistency about the 'platform' filter, which could confuse agents, and no explicit note about pagination defaults, though the schema covers page_size.

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 has 100% coverage with each parameter described, so the schema carries the heavy lifting. The description adds only a summarized list of filter types (store, platform, discount level), but interestingly 'platform' is not a parameter in the schema, which is a slight inconsistency. Overall, the description does not significantly enhance what the schema already provides.

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 clearly states the tool 'Search active game deals' with optional filters, which is a specific verb+resource. It distinguishes itself from sibling tools like search_games by focusing on deals, and the returns list (title, store, price, savings, scores) makes the purpose unambiguous.

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?

The description implies usage: it is for searching active game deals, which is clear context. However, it does not explicitly mention alternatives or exclusion criteria (e.g., 'use search_games for general game info'), leaving the comparison to siblings to be inferred.

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.