Vouchernaut

Compare a game's prices

game_prices

Read-onlyIdempotent

Every shop's price for a video game on Vouchernaut (UK accounts): official stores (Steam, PlayStation Store, Xbox, Nintendo eShop and the like) first, then key shops, for one platform and edition. Each price includes the fee the shop's feed gives, says key or download and its region, and warns where a key may not work on a UK account; each has a tracked link to the shop. A shop's discount code is never given, only its price with the code and the page that shows it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "game": "<game>"
    },
    "name": "game_prices"
  }
}

Input Schema

Name	Required	Description
`game`	Yes	The game, by name ("Elden Ring"), slug or vouchernaut.com/games page address
`limit`	No	Shops to return, in the page's order
`edition`	No	An edition ("Deluxe"); the standard one if left out
`platform`	No	A platform it's sold for ("PlayStation", "Steam", "Xbox", "Nintendo"); the first listed if left out
`key_shops`	No	Include key resellers and marketplaces (on by default)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already mark this read-only, idempotent and non-destructive, so the description is free to spend its words on behaviour it alone can supply. It does: result ordering (official stores first, then key shops), what each record carries (feed fee included, key vs download, region, UK-account warnings, tracked link), and an explicit negative — discount codes are never disclosed, only the coded price and its page.

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 sentences, each carrying new information, with the shop-ordering rule and the discount-code caveat front-loaded where an agent will read them. Dense but not padded; a slightly tighter phrasing would earn a 5.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden itself and does so — what fields each price record has, what a tracking link means, and what is deliberately withheld. For a five-parameter read tool whose annotations cover the safety profile, nothing an agent needs to call it correctly is missing.

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%, so all five parameters are already documented, and that sets the baseline at 3. The description adds only marginal meaning, chiefly that ordering is official-then-key-shop (relevant to how limit truncates results) and that results are scoped to a single platform and edition; the defaults themselves live in the schema.

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

Purpose5/5

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

The description opens with a specific verb and resource — 'Every shop's price for a video game on Vouchernaut (UK accounts)' — and pins the scope to 'one platform and edition'. That is enough for an agent to separate it from siblings such as gift_card_prices, price_drops or check_deal without opening the schema.

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 context is implied rather than stated: the UK-account caveat and the single-game/single-platform framing tell an agent roughly when this applies. But no sibling alternative is named and no when-not condition is given, so the routing decision is left to inference.

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

All Vouchernaut 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.

Resources

Need Help?