Skip to main content
Glama

AutoTasker Hub — China Social Data API

game_deals

CheapShark game deals across Steam/Epic/GOG: sale price, savings%, Metacritic. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
onSaleNo
maxPriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations, so the description carries the full load. It does add real behavioral context by disclosing the upstream source and a per-call cost ($0.01 USDC), which matters for budgeting. But it omits auth/payment mechanics, rate limits, and what is returned when no deals match the filters.

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?

Two compact clauses with no filler; the resource and returned fields are front-loaded. It is arguably too terse, but nothing is wasted.

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

Completeness2/5

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

For a 3-parameter tool with no annotations and no output schema, the description should explain what onSale and maxPrice do and how limit affects output size. Listing returned fields partially substitutes for an output schema, but the parameter gap leaves an agent guessing at filter semantics.

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?

All three parameters (limit, onSale, maxPrice) have 0% schema description coverage, and the description never mentions them. Worse, the '$0.01 USDC' cost note sits next to an undocumented maxPrice parameter, inviting confusion between the tool fee and the price filter.

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?

Names a concrete resource and source: CheapShark game deals across Steam/Epic/GOG, and enumerates the return fields (sale price, savings%, Metacritic). Clearly distinct from every listed sibling, though it doesn't state the verb explicitly (list/query).

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?

Implied usage only: an agent can infer this is for finding discounted game deals, but there is no statement of when to prefer it, no mention of how the defaults (onSale=true, maxPrice=5) shape results, and no exclusions or alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.