gamesLook up a PC game by title (or steamAppID) across CheapShark's catalog; returns the game's cheapest current deal, cheapest historical price, and list of active deal IDs across stores.
| Name | Required | Description | Default |
|---|---|---|---|
| exact | No | ||
| limit | No | ||
| title | Yes | ||
| steamAppID | No |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of items returned. | |
| items | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "title": "The Witcher 3"
+ },
+ {
+ "exact": true,
+ "limit": 5,
+ "title": "Cyberpunk 2077"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of items returned.",
+ "type": "integer"
+ },
+ "items": {
+ "items": {
+ "properties": {
+ "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"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "items",
+ "count"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, confirming safe read behavior. The description adds valuable detail about the return data: cheapest current deal, historical price, and active deal IDs. No contradictions with 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, well-structured sentence that front-loads the core purpose. Every clause is essential, with no redundancy.
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?
An output schema exists, so return structure detail is not needed. The description covers the essential aspects for a lookup tool. However, it does not explain the 'limit' parameter's effect on results, leaving a minor gap.
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?
With 0% schema description coverage, the description partially compensates by mentioning lookup by 'title (or steamAppID)', but it does not explain 'exact' or 'limit' parameters. Some added value, but insufficient for full clarity.
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 verb 'Look up', the specific resource 'PC game', and the catalog 'CheapShark'. It details the output: cheapest current deal, historical price, and active deal IDs. This distinguishes it from sibling tools like 'deals' which likely list multiple 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 implies usage when you have a game title or Steam AppID, but it lacks explicit guidance on when to use this tool versus alternatives like 'deals' or 'deal'. No exclusions or prerequisites are mentioned.
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.