Skip to main content
Glama

woebike.de Preisvergleich

by de.woebike
OverviewDiscussionsAdmin

E-Bikes in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)

search_offers
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoAuf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. "Nike").
limitNoMaximale Anzahl Ergebnisse (Default 24, max 100).
queryNoSuchbegriff, z.B. Modell/Marke/Eigenschaft ("Balkonkraftwerk 800W", "iPhone 15 schwarz"). Optional.
maxPriceNoHoechstpreis in EUR (optional).
minPriceNoMindestpreis in EUR (optional).

Output Schema

TableJSON 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. Changed11 schema fields changed
    • addedInput schema / properties / brand
      Added value: +{
+  "description": "Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\").",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximale Anzahl Ergebnisse (Default 24, max 50)."New value: +"Maximale Anzahl Ergebnisse (Default 24, max 100)."
    • changedInput schema / properties / limit / maximum
      Previous value: -50New value: +100
    • addedInput schema / properties / maxPrice
      Added value: +{
+  "description": "Hoechstpreis in EUR (optional).",
+  "type": "number"
+}
    • addedInput schema / properties / minPrice
      Added value: +{
+  "description": "Mindestpreis in EUR (optional).",
+  "type": "number"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Optionaler Suchbegriff — filtert nach Titel, Marke oder Haendler."New value: +"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional."
    • 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)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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.

Conciseness4/5

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.

Completeness5/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines4/5

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.

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