Skip to main content
Glama

PC Game Price Broker by The Company

Best prices for a list of games

compare_games
Read-only

Lowest current price for up to 10 PC games in one call, with the total. Useful for a wishlist or a gift list. Each game comes with its cheapest store, the lowest price on record and a buy link. Prices in US dollars.

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": "compare_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
gamesNoGame names, for example ["Hades", "Stardew Valley"].
game_idsNoOptional exact game ids from earlier answers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description does add useful context beyond annotations — USD pricing, a per-game cheapest store, historical low, and a buy link — though with no output schema this is largely a return-value sketch rather than behavioral detail like failure handling for unknown game names.

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?

Four short sentences, front-loaded with the core capability and scope, then use case, then return contents. No filler, though the wishlist/gift-list clause is close to expendable.

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 simple read-only batch lookup with two optional, fully documented parameters, the description covers scope, return contents and currency unit. Missing only edge-case behavior (unmatched names, partial results), which is minor for this complexity.

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?

Schema coverage is 100% and both parameters are documented in-schema, so baseline 3 applies. The description adds only the 'up to 10' cap and the USD assumption; it does not clarify the games-vs-game_ids tradeoff or what happens if a name is ambiguous.

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 resource and operation: the lowest current price for a batch of up to 10 PC games, plus a total. The phrase 'in one call' hints at batch semantics versus single-offer siblings like find_best_offer, but no sibling is named, so differentiation is implied rather than explicit.

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?

'Useful for a wishlist or a gift list' suggests a scenario but gives no explicit when-to-use/when-not rules and never mentions alternatives such as find_best_offer or top_deals. It also doesn't say when to prefer game_ids over games, leaving the choice to the agent.

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.

Resources