Cheapshark

Deals

deals

Read-onlyIdempotent

Search PC game deals across digital stores (Steam, GOG, Humble, etc.) filtered by store, price range, Metacritic score, Steam rating, title, or sale status; returns deal ID, sale price, normal price, savings %, and store.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "onSale": true,
      "sortBy": "Savings",
      "storeID": "1,2,6",
      "pageSize": 20,
      "pageNumber": 0
    },
    "name": "deals"
  }
}

Input Schema

Name	Required	Description
`AAA`	No
`desc`	No	Reverse the default best-first order — i.e. WORST first (smallest savings, lowest Metacritic, most expensive). Leave unset for top results; sending true is almost never what you want.
`exact`	No
`title`	No
`onSale`	No
`sortBy`	No	DealRating \| Title \| Savings \| Price \| Metacritic \| Reviews \| Release \| Store \| Recent. Already returns BEST-first for the field you pick (biggest Savings, highest Metacritic, cheapest Price) — you do NOT need `desc` to get the top results.
`storeID`	No	Comma-sep store IDs. See stores().
`pageSize`	No
`lowerPrice`	No
`metacritic`	No
`pageNumber`	No
`steamAppID`	No
`steamworks`	No
`upperPrice`	No
`steamRating`	No

Output Schema

Name	Required	Description	Default
`count`	No	Number of items returned.
`items`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 1, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "desc": true,
-    "onSale": true,
-    "pageNumber": 0,
-    "pageSize": 20,
-    "sortBy": "Savings",
-    "storeID": "1,2,6"
-  },
-  {
-    "AAA": true,
-    "lowerPrice": 20,
-    "metacritic": 80,
-    "title": "Elden Ring",
-    "upperPrice": 60
-  }
-]New value: +[
+  {
+    "onSale": true,
+    "pageNumber": 0,
+    "pageSize": 20,
+    "sortBy": "Savings",
+    "storeID": "1,2,6"
+  },
+  {
+    "AAA": true,
+    "lowerPrice": 20,
+    "metacritic": 80,
+    "title": "Elden Ring",
+    "upperPrice": 60
+  }
+]

addedInput schema / properties / desc / description

Added value: +"Reverse the default best-first order — i.e. WORST first (smallest savings, lowest Metacritic, most expensive). Leave unset for top results; sending true is almost never what you want."

changedInput schema / properties / sortBy / description

Previous value: -"DealRating | Title | Savings | Price | Metacritic | Reviews | Release | Store | Recent"New value: +"DealRating | Title | Savings | Price | Metacritic | Reviews | Release | Store | Recent. Already returns BEST-first for the field you pick (biggest Savings, highest Metacritic, cheapest Price) — you do NOT need `desc` to get the top results."

Changed8 schema fields changedJun 2, 2026
- changedOutput schema / properties / count / type
```
Previous value: -"integer"New value: +"number"
```
- addedOutput schema / properties / items / items / properties / internalName
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / items / items / properties / isOnSale / type
```
Previous value: -"boolean"New value: +"string"
```
- addedOutput schema / properties / items / items / properties / metacriticLink
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / items / items / properties / steamAppID
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / items / items / properties / steamRatingCount
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / items / items / properties / steamRatingText / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / required
```
Removed value: -[
-  "items",
-  "count"
-]
```

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "desc": true,
+    "onSale": true,
+    "pageNumber": 0,
+    "pageSize": 20,
+    "sortBy": "Savings",
+    "storeID": "1,2,6"
+  },
+  {
+    "AAA": true,
+    "lowerPrice": 20,
+    "metacritic": 80,
+    "title": "Elden Ring",
+    "upperPrice": 60
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "dealID": {
+            "description": "Unique deal identifier",
+            "type": "string"
+          },
+          "dealRating": {
+            "description": "Deal rating score",
+            "type": "string"
+          },
+          "gameID": {
+            "description": "Game ID associated with deal",
+            "type": "string"
+          },
+          "isOnSale": {
+            "description": "Whether deal is currently on sale",
+            "type": "boolean"
+          },
+          "lastChange": {
+            "description": "Unix timestamp of last change",
+            "type": "number"
+          },
+          "metacriticScore": {
+            "description": "Metacritic score",
+            "type": "string"
+          },
+          "normalPrice": {
+            "description": "Normal retail price",
+            "type": "string"
+          },
+          "releaseDate": {
+            "description": "Unix timestamp of release date",
+            "type": "number"
+          },
+          "salePrice": {
+            "description": "Current sale price",
+            "type": "string"
+          },
+          "savings": {
+            "description": "Savings percentage",
+            "type": "string"
+          },
+          "steamRatingPercent": {
+            "description": "Steam rating percentage",
+            "type": "string"
+          },
+          "steamRatingText": {
+            "description": "Steam rating text",
+            "type": "string"
+          },
+          "storeID": {
+            "description": "Store identifier",
+            "type": "string"
+          },
+          "thumb": {
+            "description": "Thumbnail image URL",
+            "type": "string"
+          },
+          "title": {
+            "description": "Deal title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read nature is covered. The description adds meaningful context about the search scope, filters, and returned deal fields, but does not disclose potential rate limits, pagination behavior, or other edge-case traits.

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?

A single sentence that front-loads the core purpose and packs in filters and return fields with zero filler. Every phrase earns its place and the structure is immediately scannable.

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?

The description, combined with annotations and an output schema, gives a solid foundation: filters, return fields, and safe/idempotent semantics are covered. It lacks explicit mention of sorting and pagination, but those are present in the schema/examples, so the overall package is nearly complete for a search tool.

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?

Schema description coverage is only 20%, so the description must compensate. It adds semantics for several filters (store, price range, Metacritic score, Steam rating, title, sale status) but does not map these to exact parameter names or cover important parameters like sortBy, pageSize, pageNumber, exact, and steamAppID. Partial compensation for low schema coverage, but significant gaps remain.

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 states a specific action ('Search PC game deals') with a clear resource scope ('across digital stores') and enumerates filter dimensions and return fields. It clearly distinguishes itself from siblings like 'deal' (which likely retrieves a single deal) and 'stores' (which lists store IDs).

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 through its filter list but does not explicitly state when to use this tool versus alternatives such as 'deal', 'stores', or 'games'. No exclusions or alternative-recommendation are provided, leaving the agent to infer context from sibling names.

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

All Cheapshark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.