Skip to main content
Glama
Sign In

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

by com.gameshopenter
OverviewDiscussionsAdmin

Get one product by SKU

get_product
Read-onlyIdempotent

Fetch current price, stock and details for one Gameshop Enter product by its SKU (as returned by search_products). Includes the product-page URL (url) and a direct checkout link (checkoutUrl) that puts the item in the cart and opens checkout; with the buyer's country, url and local follow that country as in search_products.

Input Schema

NameRequiredDescriptionDefault
skuYesProduct SKU, e.g. "GBA-177714825902"
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.

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. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context about what the returned checkoutUrl does (adds to cart, opens checkout) and that url/local follow the buyer's country, but says nothing about failure modes for unknown SKUs or out-of-stock items.

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 sentences that lead with the action and its scope, with no filler. The trailing country clause is somewhat compressed and slightly redundant with the schema, but it is not wasted space.

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?

There is no output schema, so the description carries the return-value burden, and it does so reasonably by naming price, stock, details, url and checkoutUrl. Missing only edge-case behavior (unknown SKU, stale stock), which is minor for a simple read.

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 the country parameter's description is already very detailed, so the description only restates it in compressed form. With the schema doing the heavy lifting, baseline 3 applies; the "as returned by search_products" hint for sku is the only marginal addition.

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?

States a specific verb and resource — fetching current price, stock and details for one product by SKU — and explicitly ties the SKU to search_products, so it is distinguishable from that sibling at a glance. It also names the extra artifacts (url, checkoutUrl) the caller gets back.

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?

The "SKU (as returned by search_products)" phrasing implicitly routes the agent here after a search, and the country note explains the variant-selection behavior. It stops short of explicitly stating when not to use it or how it differs from get_quote/store_info.

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