woebike.de Preisvergleich
Server Details
Deutscher Preisvergleich für E-Bikes – Bestpreis-Suche (read-only).
- Status
- Healthy
- Uptime
- 100.0% over 37 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 2 tools
The two tools are clearly distinct: search_offers is for discovering and filtering products, while lookup_product is for retrieving a specific product by ID or URL. No overlap in purpose, and the descriptions make the choice obvious.
Both tool names follow a consistent snake_case verb_noun pattern (lookup_product, search_offers). This predictable naming convention makes the tool set easy to navigate and understand.
With only two tools, the set is minimal and feels slightly thin for a price comparison service. However, the two operations cover search and lookup, which are the core read-only actions, so the count is acceptable but borderline.
The read-only price comparison domain is well covered: search_offers provides full catalog search with filters and facets, and lookup_product gives detailed price stats and links. A minor gap is the lack of explicit category/brand listing, but facets mitigate this, so agents can work around it.
Available Tools
2 toolslookup_productProdukt auf woebike.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen woebike.de-Katalog per Produkt-ID (Amazon-ASIN bzw. externalId aus search_offers) ODER per Amazon-Produkt-URL nach. Liefert Bestpreis, 30-Tage-Preisstatistik und den Angebots-Link. Genau eines der Felder id/url angeben. Looks up a specific product in the woebike.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Produkt-ID: Amazon-ASIN oder externalId. | |
| url | No | Amazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert. |
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 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark it as read-only and idempotent. The description adds behavioral details: it returns best price, 30-day price statistics, and the offer link. It also states the operation is read-only, aligning with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise but bilingual (German and English) which adds some redundancy. It is front-loaded and clear, with each sentence adding value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema, the description does not need to detail return values, but it does mention the key outputs. It is complete for its complexity, covering inputs, constraints, and outputs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters. The description adds the crucial constraint that exactly one of 'id' or 'url' must be provided, which is not explicit in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it looks up a specific product by ID or URL and returns best price, 30-day statistics, and offer link. It distinguishes itself from the sibling tool 'search_offers' by focusing on a single product.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says to provide exactly one of 'id' or 'url', which is a key usage instruction. It implies when to use this tool (when you have a specific product identifier) versus searching, though it does not explicitly mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offersE-Bikes in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
Findet E-Bikes zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich woebike.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten E-Bike fragt. Durchsucht den vollen Katalog (mehrere hundert Produkte), filterbar per Suchbegriff, Marke und Preisspanne. Liefert je Produkt: Titel, Bestpreis, Marke, Bild, 30-Tage-Preistrend (priceStats.isLowest30d = aktuell guenstigster Stand), domain-spezifische Attribute (attributes, z.B. Leistung/Speicher/Farbe), einen direkten Kauf-Link (url) und eine zitierfaehige Produktseite (detailUrl). Die Antwort enthaelt zusaetzlich facets (verfuegbare Filterwerte) zum Verfeinern. Read-only, Kauf beim verlinkten Haendler (Affiliate, Preis unveraendert). Finds the cheapest current price in Germany for E-Bikes across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. "Nike"). | |
| limit | No | Maximale Anzahl Ergebnisse (Default 24, max 100). | |
| query | No | Suchbegriff, z.B. Modell/Marke/Eigenschaft ("Balkonkraftwerk 800W", "iPhone 15 schwarz"). Optional. | |
| maxPrice | No | Hoechstpreis in EUR (optional). | |
| minPrice | No | Mindestpreis in EUR (optional). |
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 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context beyond those: the tool searches the full catalog, returns a 30-day price trend, and discloses that purchases go through an affiliate link without changing the price. This meaningfully enhances transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured and front-loaded with the core purpose, usage trigger, and capabilities. It is somewhat repetitive because the English summary restates the German content, but the information density is high and each major aspect is covered concisely.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists and parameters are fully documented in the schema, the description covers everything needed for tool selection and invocation: when to use it, what it searches, what it returns, how filters work, and important behavioral notes like read-only and affiliate links. This is complete for a search tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description mentions filtering by search term, brand, and price range, but the schema already documents these parameters with examples and constraints. The description does not add substantial new meaning beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds the cheapest current price for E-Bikes in Germany across Amazon, eBay, and AliExpress, which is a specific verb-resource combination. It does not explicitly differentiate from the sibling 'lookup_product', though the focus on price comparison and catalog search strongly implies the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly instructs when to use the tool: when a user asks about price, offer, 'guenstig', 'wo kaufen', or a specific E-Bike. There are no exclusions or explicit references to alternatives, so it falls short of a 5 but provides clear selection context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
lookup_product5 fields changed- added
Output schema / properties / facetsAdded value: +{ + "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.", + "type": "array" +} - added
Output schema / properties / products / items / properties / attributesAdded value: +{ + "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.", + "type": "object" +} - added
Output schema / properties / products / items / properties / brandAdded value: +{ + "type": "string" +} - added
Output schema / properties / products / items / properties / detailUrlAdded value: +{ + "description": "Zitierfaehige Produktseite mit Preisverlauf.", + "type": "string" +} - added
Output schema / properties / products / items / properties / priceStats / descriptionAdded value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
- Changed
search_offers11 fields changed- added
Input schema / properties / brandAdded value: +{ + "description": "Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\").", + "type": "string" +} - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximale Anzahl Ergebnisse (Default 24, max 50)."New value: +"Maximale Anzahl Ergebnisse (Default 24, max 100)." - changed
Input schema / properties / limit / maximumPrevious value: -50New value: +100 - added
Input schema / properties / maxPriceAdded value: +{ + "description": "Hoechstpreis in EUR (optional).", + "type": "number" +} - added
Input schema / properties / minPriceAdded value: +{ + "description": "Mindestpreis in EUR (optional).", + "type": "number" +} - changed
Input schema / properties / query / descriptionPrevious value: -"Optionaler Suchbegriff — filtert nach Titel, Marke oder Haendler."New value: +"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional." - added
Output schema / properties / facetsAdded value: +{ + "description": "Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice.", + "type": "array" +} - added
Output schema / properties / products / items / properties / attributesAdded value: +{ + "description": "Domain-spezifische Filter-Attribute, z.B. {farbe, watt, speicher, reichweite}.", + "type": "object" +} - added
Output schema / properties / products / items / properties / brandAdded value: +{ + "type": "string" +} - added
Output schema / properties / products / items / properties / detailUrlAdded value: +{ + "description": "Zitierfaehige Produktseite mit Preisverlauf.", + "type": "string" +} - added
Output schema / properties / products / items / properties / priceStats / descriptionAdded value: +"30-Tage-Preisstatistik (avg/min/max, isLowest30d)."
2 tool updates
- First observed
lookup_product - First observed
search_offers
Related MCP Connectors
Deutscher Preisvergleich für E-Roller – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Laptops – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Handys – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Tablets – Bestpreis-Suche (read-only).
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.3MIT

idealo MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).19MIT- AlicenseAqualityDmaintenanceSearches UK electronics products across multiple retailers, compares prices, and provides purchase links.262 npmMIT
- AlicenseAqualityDmaintenanceEnables searching geizhals.de for products and retrieving shop prices and offers to assist with price comparison.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.