Skip to main content
Glama

woebike.de Preisvergleich

by de.woebike

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 ~150 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

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare readOnly, idempotent, non-destructive; description adds specific behavioral details: reads ~150 products, provides price trend (priceStats.isLowest30d), domain-specific attributes, and direct purchase link. No annotation contradiction.

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

Conciseness3/5

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

Description is verbose (German and English), includes repeated information and overly detailed output descriptions. Could be more concise while retaining key points.

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 5 parameters, output schema, and annotations, the description provides complete context: purpose, usage, behavior, parameter linkage, output structure, and safety. No gaps.

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% (all 5 parameters described). The description mentions filtering by search term, brand, and price range, which maps to parameters but adds no new semantic detail beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states the tool finds cheapest current prices for E-Bikes in Germany across Amazon, eBay, and AliExpress (specific verb 'findet' and resource). It distinguishes from sibling 'lookup_product' by emphasizing price comparison.

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?

Explicitly states 'use this tool when a user asks for price, offer, cheap, where to buy, or a specific E-Bike'. Does not mention when not to use or alternatives, but provides clear 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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: search_offers is for discovering and filtering E-Bikes, while lookup_product is for retrieving detailed price and stats for a specific product. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern (search_offers, lookup_product) and use snake_case, making them predictable and easy to understand.

Tool Count3/5

With only two tools, the server is quite minimal. While they cover the core functionality of search and product lookup, the scope feels thin for a full-featured price comparison service. A few more tools (e.g., list brands, compare products) would be appropriate.

Completeness3/5

The server covers the main use cases of searching and looking up products, but lacks tools for browsing all products, comparing multiple products, or accessing full price history. These gaps are notable but can be partially worked around.

Resources