gameFetch full deal and price-history details for a single CheapShark game by its numeric game ID; returns all active store deals, cheapest price ever, and Steam rating info.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| deals | No | ||
| thumb | No | Game thumbnail URL | |
| title | No | Game title | |
| gameID | No | Game identifier | |
| steamAppID | No | Steam app ID if available | |
| cheapestPriceEver | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "id": "379720"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "cheapestPriceEver": {
+ "properties": {
+ "date": {
+ "description": "Unix timestamp of cheapest price",
+ "type": "number"
+ },
+ "price": {
+ "description": "Cheapest price ever recorded",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "deals": {
+ "items": {
+ "properties": {
+ "dealID": {
+ "description": "Deal identifier",
+ "type": "string"
+ },
+ "dealRating": {
+ "description": "Deal rating",
+ "type": "string"
+ },
+ "isOnSale": {
+ "description": "Whether on sale",
+ "type": "boolean"
+ },
+ "lastChange": {
+ "description": "Unix timestamp of last change",
+ "type": "number"
+ },
+ "normalPrice": {
+ "description": "Normal price",
+ "type": "string"
+ },
+ "price": {
+ "description": "Current deal price",
+ "type": "string"
+ },
+ "savings": {
+ "description": "Savings percentage",
+ "type": "string"
+ },
+ "storeID": {
+ "description": "Store identifier",
+ "type": "string"
+ },
+ "storeIcon": {
+ "description": "Store icon URL",
+ "type": "string"
+ },
+ "url": {
+ "description": "Deal URL",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "gameID": {
+ "description": "Game identifier",
+ "type": "string"
+ },
+ "steamAppID": {
+ "description": "Steam app ID if available",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "thumb": {
+ "description": "Game thumbnail URL",
+ "type": "string"
+ },
+ "title": {
+ "description": "Game title",
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool as readOnly, openWorld, idempotent, and non-destructive. The description adds meaningful behavioral context by specifying the exact data returned: 'all active store deals, cheapest price ever, and Steam rating info', which goes 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that front-loads the action ('Fetch') and efficiently conveys all necessary information. No extraneous words or repetition.
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 presence of an output schema (mentioned in context signals), the description does not need to detail return values. It adequately covers the tool's functionality: fetching full deal details, price history, and Steam rating for a single game ID.
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?
The input schema has 0% coverage in the description, but the description compensates by stating the parameter is a 'numeric game ID', clarifying its purpose. Though it doesn't explicitly define the format, it adds meaning beyond the raw schema type ('string') and example.
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 clearly states the action ('Fetch'), the resource ('full deal and price-history details for a single CheapShark game'), and the method ('by its numeric game ID'). It distinguishes itself from siblings like 'games' (which likely lists multiple) and 'deals' (which may focus on deals).
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 implicitly advises when to use the tool: when you have a specific game ID and need comprehensive details. It does not explicitly contrast with alternatives like 'games' or 'deal', but the context is clear enough for an agent to infer proper usage.
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.