Skip to main content
Glama

wostrom.de Preisvergleich

Look up one partner offer on wostrom.de

lookup_product
Read-onlyIdempotent

Returns the current price and links of ONE partner offer that search_offers returned before. USE WHEN you need to re-check the price of an offer from an earlier search_offers result. Do not use it to search – use search_offers. PARAMETERS: "id" = externalId from search_offers, or "url" = the product URL. EXAMPLE: {"id":""}. RETURNS: the same structure as search_offers with at most one entry in products[] (empty if the offer is gone).

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

Input Schema

NameRequiredDescriptionDefault
idNoOffer ID: externalId from search_offers.
urlNoAlternatively the product URL (optional).
languageNoLanguage of the linked pages (ISO 639-1, e.g. "de", "en", "tr", "ar", "fr"). Set it to the user's language. Default: Accept-Language header, otherwise "de"; unsupported languages fall back to "en".

Output Schema

NameRequiredDescriptionDefault
siteNo
countYes
queryNo
facetsNoVerfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.
productsYes
updatedAtNo
disclosureNo
catalogVersionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Produkt-ID / product ID (externalId aus search_offers)."New value: +"Offer ID: externalId from search_offers."
    • changedInput schema / properties / language / description
      Previous value: -"Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en."New value: +"Language of the linked pages (ISO 639-1, e.g. \"de\", \"en\", \"tr\", \"ar\", \"fr\"). Set it to the user's language. Default: Accept-Language header, otherwise \"de\"; unsupported languages fall back to \"en\"."
    • changedInput schema / properties / url / description
      Previous value: -"Alternativ eine Produkt-URL / product URL (optional)."New value: +"Alternatively the product URL (optional)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Antwortsprache / response language (de|en). Default: Accept-Language, sonst de."New value: +"Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en."
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "de",
      -  "en"
      -]New value: +[
      +  "de",
      +  "en",
      +  "tr",
      +  "ar",
      +  "ru",
      +  "pl",
      +  "uk",
      +  "fr",
      +  "es",
      +  "it",
      +  "pt",
      +  "nl",
      +  "ro",
      +  "el",
      +  "hr",
      +  "cs",
      +  "hu",
      +  "fa",
      +  "zh",
      +  "ja"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Produkt-ID: Amazon-ASIN oder externalId."New value: +"Produkt-ID / product ID (externalId aus search_offers)."
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Antwortsprache / response language (de|en). Default: Accept-Language, sonst de.",
      +  "enum": [
      +    "de",
      +    "en"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"Amazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert."New value: +"Alternativ eine Produkt-URL / product URL (optional)."
  4. Changed5 schema fields changed
    • addedOutput schema / properties / facets
      Added value: +{
      +  "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.",
      +  "type": "array"
      +}
    • addedOutput schema / properties / products / items / properties / attributes
      Added value: +{
      +  "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / products / items / properties / brand
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / products / items / properties / detailUrl
      Added value: +{
      +  "description": "Zitierfaehige Produktseite mit Preisverlauf.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / products / items / properties / priceStats / description
      Added value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
  5. First observed

TDQS

A4.4/5.0
Behavior4/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 description's added value is the cardinality and absence semantics: at most one entry in products[], empty when the offer is gone. That is genuinely useful failure-mode information not present in the structured fields. It stops short of noting any caching or staleness behavior for the "current price" claim, keeping it below a 5.

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?

Well structured with front-loaded USE WHEN, then parameters, return shape, and an example. The PARAMETERS section duplicates the schema descriptions verbatim in spirit, which is mild waste, but nothing is buried or padded.

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?

An output schema exists, yet the description still communicates the one thing an agent needs about returns: a single-entry products[] that may be empty. Combined with the routing guidance and the identifier provenance, an agent has everything required to call this correctly.

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 the baseline is 3; the description's PARAMETERS line and the JSON example largely restate what the schema already documents (id = externalId from search_offers, url = product URL). The example adds a small amount of practical value but no new semantics, notably nothing about what happens when both id and url are supplied or omitted given zero required parameters.

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?

Opens with a specific verb and resource ("Returns the current price and links of ONE partner offer") and explicitly scopes it to offers that came from a prior search_offers result. The capitalized ONE plus the named sibling makes the distinction from search_offers unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit use case ("USE WHEN you need to re-check the price of an offer from an earlier search_offers result") and an explicit exclusion ("Do not use it to search – use search_offers"). It also tells the agent which identifier to supply and where it came from, so routing and invocation are both covered.

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