Cheapshark

Cheapshark Games

cheapshark_games

Read-onlyIdempotent

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

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": {
      "title": "The Witcher 3"
    },
    "name": "cheapshark_games"
  }
}

Input Schema

Name	Required	Description	Default
`exact`	No
`limit`	No
`title`	Yes
`steamAppID`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the shape of the result (cheapest current deal, cheapest historical price, active deal IDs), but says nothing about what happens when a title matches nothing or matches multiple games — a material behavior for a lookup tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the lookup key and the returned data categories come first. The semicolon-joined return summary is dense but every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return values need not be spelled out, and annotations cover the safety profile. The remaining gaps are the undocumented 'exact' and 'limit' parameters and the no-match/ambiguous-match behavior, which together leave the definition adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it only clarifies two of four parameters: 'title' and 'steamAppID' as alternative lookup keys. The 'exact' boolean (presumably exact vs fuzzy title matching) and 'limit' (presumably max results) are never explained in either place, leaving their semantics to guesswork.

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?

States a specific verb and resource ('Look up a PC game') plus the data domain ('across CheapShark's catalog'), which is concrete enough to distinguish it from generic deal-listing siblings. It does not, however, explicitly contrast itself with the similarly named 'cheapshark_game' sibling, so an agent must infer the singular/plural split.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance and no named alternative for a single-game lookup versus a broader deals query. The only routing hint is 'by title (or steamAppID)', which concerns parameter choice rather than tool choice.

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.