wokonsole.de Preisvergleich

Partner-Angebot auf wokonsole.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.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, and the description's only behavioral claim, 'Read-only', merely restates them. Nothing is said about what happens when an ID is unknown (error vs empty result), whether id and url can be combined or which wins, or how url-only lookups behave.

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?

The essential fact (lookup by externalId from search_offers) is front-loaded, and the bilingual DE/EN duplication is justified for a German-language partner tool. The trailing 'Read-only' is wasted given the annotations, so it falls short of fully economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and all three parameters are documented in the schema. What remains unaddressed is the notable fact that zero parameters are required, leaving the agent unsure whether id or url must be supplied or what happens if neither is.

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 the schema already explains id, url and the language default/fallback rules in detail, and the baseline 3 applies. The description adds only the mapping of id to 'externalId from search_offers' and says nothing about the url alternative or precedence between the two optional parameters.

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?

States a specific verb and resource ('looks up a partner offer') and anchors it to the sibling that produces the ID ('from search_offers by its ID (externalId)'). An agent can distinguish it from search_offers without opening the schema, though find_pages is never contrasted and the ID-vs-URL entry path is left ambiguous.

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?

Naming search_offers as the source of the externalId implicitly tells the agent this tool is a follow-up to a search, which is a genuine usage cue. But there is no explicit when-to-use, no exclusion (e.g. when to prefer find_pages), and no statement about whether id or url is the intended entry point.

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

All wokonsole.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?