wospeicher.de Preisvergleich

Partner-Angebot auf wospeicher.de nachschlagen / look up offer

lookup_product

Read-onlyIdempotent

Schlaegt ein Partner-Angebot aus search_offers per Produkt-ID (externalId) nach. EN: Looks up a partner offer from search_offers by its ID (externalId). Read-only.

Input Schema

Name	Required	Description
`id`	No	Produkt-ID / product ID (externalId aus search_offers).
`url`	No	Alternativ eine Produkt-URL / product URL (optional).
`language`	No	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.

Output Schema

Name	Required	Description
`site`	No
`count`	Yes
`query`	No
`facets`	No	Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.
`products`	Yes
`updatedAt`	No
`disclosure`	No
`catalogVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

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"
+]

Changed3 schema fields changedOct 28, 2026

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)."

Changed5 schema fields changedJul 7, 2026

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)."
```

First observedJul 6, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description only repeats 'Read-only' and adds no behavioral context beyond annotations, such as permissions, rate limits, or what happens with the alternative URL parameter.

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

Conciseness5/5

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

The description is two short bilingual sentences, front-loads the lookup purpose, and contains no unnecessary text. The redundant 'Read-only' is minor.

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?

Given the rich annotations, full schema descriptions, and an output schema, the description is largely complete for a simple lookup tool. Its main gap is not explicitly routing the agent between this tool and its siblings, but that is partly covered by the schema and tool name.

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 description coverage is 100%, so all three parameters are fully documented in the schema. The description mentions the ID/externalId lookup but adds no extra semantic detail about the optional URL or language parameters beyond what the schema already provides.

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?

The description states a specific verb and resource: looking up a partner offer from search_offers by product ID (externalId). This reasonably distinguishes it from search_offers, which is implied to be the search source, though the differentiation is implicit rather than explicit.

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 implies the tool is used when you already have a product ID from search_offers, but it does not explicitly say when to use this versus search_offers or find_pages. No exclusions or prerequisites are stated.

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

All wospeicher.de Preisvergleich 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?