Skip to main content
Glama
Sign In

Gameshop Enter — retro Nintendo & Pokémon TCG (EU)

by com.gameshopenter
OverviewDiscussionsAdmin

Search the Gameshop Enter catalog

search_products
Read-onlyIdempotent

Search the live catalog of Gameshop Enter — original retro Nintendo games, consoles, PlayStation 4/5 games and Pokémon TCG, all personally tested, shipping to all 27 EU countries plus Monaco, to 17 countries outside the EU with their own store (US, CH, AU, NZ, HK, SG, LI, IL, AE, SA, QA, KW, CA, PR, CL, GB, MX) and to 174 more countries worldwide. Understands abbreviations ("gba"), Dutch and English game names, typos, and Pokémon version names in German, French, Italian and Spanish ("pokemon feuerrot", "pokémon rubis"). Returns products with price in EUR, stock status, the product-page URL (url) and a direct checkout link (checkoutUrl) that puts the item in the cart and opens checkout. Pass the buyer's country to get the product pages of that country's own store with the price in its currency (local), or the product pages in the buyer's language.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, cap 25)
queryYesGame title, character, franchise or SKU
countryNoOptional ISO-2 country of the buyer, e.g. "SG", "US", "AU", "DE". A country with its own store (US, CA, AU, NZ, SG, HK, CH, IL, AE, SA …) gets url on that store and, where that store charges in its own currency, local with the price in it (SGD for SG); another country gets url in its own language (German for DE). Omit for the Dutch product page in EUR.
maxPriceNoOptional maximum price in EUR
platformNoOptional platform filter, e.g. "Game Boy Advance", "N64", "Switch"; abbreviations work too (ds, 3ds, gba, gbc, snes, nes, wii, wii u, gamecube, ps4, ps5, tcg). "ds" means Nintendo DS only (not 3DS), "wii" means Wii only (not Wii U).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Optional ISO-2 country of the buyer, e.g. \"SG\", \"US\", \"AU\", \"DE\". A country with its own store (US, CA, AU, NZ, SG, HK, CH, IL, AE, SA …) gets url on that store and, where that store charges in its own currency, local with the price in it (SGD for SG); another country gets url in its own language (German for DE). Omit for the Dutch product page in EUR.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / platform / description
      Previous value: -"Optional platform filter, e.g. \"Game Boy Advance\", \"N64\", \"Switch\""New value: +"Optional platform filter, e.g. \"Game Boy Advance\", \"N64\", \"Switch\"; abbreviations work too (ds, 3ds, gba, gbc, snes, nes, wii, wii u, gamecube, ps4, ps5, tcg). \"ds\" means Nintendo DS only (not 3DS), \"wii\" means Wii only (not Wii U)."
  3. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description goes well beyond them: it discloses the returned fields (price in EUR, stock status, url, checkoutUrl), explains that checkoutUrl has a cart side effect and opens checkout, and describes how currency and store domain vary with the country argument. That is exactly the behavioral context the annotations cannot convey.

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

Conciseness2/5

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

The purpose is front-loaded, but a large share of the text is marketing and shipping minutiae ("personally tested", 27 EU countries, a 17-country enumeration, 174 more countries) that has no bearing on whether or how to call the tool. That enumeration also duplicates the `country` schema description, so the length is not justified.

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, the description correctly compensates by naming the return fields and the checkoutUrl side effect, and it explains country-dependent behavior. It falls short only on sibling routing — nothing tells the agent when to escalate to get_product, get_quote or store_info.

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 earns more by adding that `query` understands abbreviations ("gba"), Dutch/English names, typos and Pokémon names in German, French, Italian and Spanish. It also restates the country's local-currency/store behavior already documented in the schema, which is redundant but harmless.

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?

Opens with a specific verb+resource: "Search the live catalog of Gameshop Enter" and scopes it to retro Nintendo, PlayStation and Pokémon TCG products. An agent can distinguish it from get_product (single-item lookup) by inference, but the description never names or contrasts the sibling explicitly.

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?

It gives useful in-parameter guidance ("Pass the buyer's country to get the product pages of that country's own store...") and notes the query engine tolerates abbreviations, typos and non-English names. However, it never says when to prefer this over get_product or store_info, and offers no exclusions or prerequisites.

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

All Gameshop Enter — retro Nintendo & Pokémon TCG (EU) toolsInspect
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