Cheapshark

Cheapshark Game

cheapshark_game

Read-onlyIdempotent

Fetch 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.

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": {
      "id": "379720"
    },
    "name": "cheapshark_game"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description
`deals`	No
`thumb`	No	Game thumbnail URL
`title`	No	Game title
`gameID`	No	Game identifier
`steamAppID`	No	Steam app ID if available
`cheapestPriceEver`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds what the call actually returns: all active store deals, cheapest price ever, and Steam rating info. It does not mention rate limits, caching, or behavior for an unknown/nonexistent ID, which is the remaining gap for an open-world fetch.

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 front-loaded sentence with a semicolon that packs purpose, scope, and return contents with zero filler. Nothing is redundant or buried.

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?

For a one-parameter read tool with an output schema and full annotations, the description covers purpose and return shape adequately. It falls just short of complete by omitting how the numeric game ID is obtained and what happens on an invalid ID.

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?

There is one parameter with 0% schema description coverage, so the description must carry it. It does add meaning by specifying the ID is a numeric game ID (not a deal ID or store ID), which is more than the bare {'id': string} schema says, but it does not explain where to obtain that ID or how to handle a bad value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('Fetch') with a precise resource ('full deal and price-history details for a single CheapShark game'), and the phrase 'single ... by its numeric game ID' implicitly distinguishes it from list-style siblings such as cheapshark_games or deals. It never names those siblings outright, so differentiation still requires a small inference.

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?

Usage is only implied by 'single ... by numeric game ID' – an agent can infer this is the detail-lookup counterpart to a listing/search tool, but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites or ID-sourcing guidance is given.

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.