Skip to main content
Glama

Compare gift card and membership prices

gift_card_prices
Read-onlyIdempotent

Prices for PlayStation Store (PSN), Xbox and Nintendo eShop gift cards and for PS Plus, Xbox Game Pass and Nintendo Switch Online membership codes, for UK or US accounts, at the shops Vouchernaut checks. Name one card ("£20 PSN card", "Game Pass Ultimate 3 months") for every shop's price for it, beside the platform's own price; name a group ("PSN gift cards", "PS Plus", "Game Pass") for every value or membership in it, each at its cheapest shop. Prices include the fee each shop's feed gives; each has a tracked link to the shop.

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": {
      "card": "<card>"
    },
    "name": "gift_card_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardYesA card, a membership or a group: "£50 PSN card", "PS Plus Extra 12 months", "PSN gift cards", "Nintendo eShop", or a vouchernaut.com/games/cards page address
limitNoShops to return for one card, in the page's order; a group lists every card
marketNoUK (gb, the default) or US accountsgb

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: prices are fee-inclusive per the shop's feed, each result carries a tracked link, and single-card results are shown beside the platform's own price — details not derivable from annotations or schema.

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 dense but well-ordered sentences: scope and coverage first, then the single-card vs group distinction, then how prices are computed and delivered. It is long and the parenthetical example lists are heavy, but essentially every clause carries operational information.

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?

With no output schema and only three parameters, the description must carry the return-shape burden, and it does: per-shop price, comparison to platform price, cheapest-shop selection for groups, and tracked links. Pagination/ordering for group results beyond 'every card' is the only notable gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes further by showing the range of acceptable 'card' inputs (a single card like "£20 PSN card", a membership like "Game Pass Ultimate 3 months", or a group like "PSN gift cards") and by clarifying that group mode returns every card at its cheapest shop, which affects how 'limit' behaves in practice.

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 names the specific resource (PlayStation Store, Xbox, Nintendo eShop gift cards plus PS Plus, Game Pass and Switch Online membership codes) and the specific verb/scope (comparing shop prices against the platform's own price). It also covers both regions and both query modes, so an agent can distinguish it from a plain game-price lookup 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 Guidelines4/5

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

It clearly states the two invocation modes — name a single card to get every shop's price for that item, or name a group to get every value/membership in it at its cheapest shop — with concrete example strings. What is missing is explicit routing against the obvious sibling game_prices (gift cards/memberships vs. games), which the agent has to infer from the resource wording.

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