Skip to main content
Glama

wolaptop.de Preisvergleich

Server Details

Deutscher Preisvergleich für Laptops – Bestpreis-Suche (read-only).

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: search_offers performs broad searches for laptops with multiple filters, while lookup_product retrieves details for a specific product by ID or URL. There is no overlap in functionality.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern using snake_case: 'lookup_product' and 'search_offers'. This makes the action and target immediately clear.

Tool Count3/5

With only two tools, the server is minimal but functional for basic price comparison. The tools cover search and detail lookup, which is reasonable for a focused domain, though additional tools like category listing or price history could enhance completeness.

Completeness4/5

The server covers the essential workflows: finding products by search and retrieving detailed price info for a specific product. Minor gaps like lacking a tool to compare multiple products or view trending items, but core operations are present.

Available Tools

2 tools
lookup_productProdukt auf wolaptop.de per ID/URL nachschlagenA
Read-onlyIdempotent
Inspect

Schlaegt ein konkretes Produkt im aktuellen wolaptop.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 wolaptop.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).

ParametersJSON Schema
NameRequiredDescriptionDefault
idNoProdukt-ID: Amazon-ASIN oder externalId.
urlNoAmazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert.

Output Schema

ParametersJSON Schema
NameRequiredDescription
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.5/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 that the operation is read-only and mentions returned data (best price, 30-day stats, offer link), which is consistent and adds value.

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 somewhat lengthy due to bilingual text (German and English), but the key information is front-loaded and each sentence adds value. Could be slightly more concise.

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 presence of an output schema and annotations, the description captures essential behavioral and usage details. It covers what the tool does, its inputs, and outputs, making it complete for a simple lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes both parameters (id and url). The description adds that exactly one field must be used and explains that externalId comes from search_offers, enhancing understanding beyond schema definitions.

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 specifies the tool looks up a product by ID or Amazon URL, and distinguishes it from the sibling tool 'search_offers' which is likely a broader search. The verb 'look up' and resource 'product' are explicit.

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?

The description states that exactly one of 'id' or 'url' must be provided, which is a clear usage rule. However, it does not explicitly say when to use this tool over the sibling 'search_offers' or mention exclusions, though the context implies it.

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

search_offersLaptops in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)A
Read-onlyIdempotent
Inspect

Findet Laptops zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wolaptop.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Laptop 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 Laptops across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.

ParametersJSON 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

ParametersJSON Schema
NameRequiredDescription
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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint true. The description adds context about searching ~150 products, filtering capabilities, return fields (title, best price, brand, price trend, attributes, links), and the read-only affiliate nature. This goes beyond annotations by explaining scope and output structure.

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?

The description is informative but includes both German and English versions, making it longer than necessary. It is front-loaded with purpose and usage guidance, but the bilingual repetition reduces conciseness. Could be tightened to a single language.

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 existence of an output schema, the description does not need to detail return values. It covers parameters, usage guidance, data sources, and constraints. The tool is well-contextualized for a search tool with comprehensive filtering details.

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% with detailed parameter descriptions. The description adds only a high-level summary ('filterbar per Suchbegriff, Marke und Preisspanne'), which does not provide new meaning beyond the schema. Baseline score 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 explicitly states it finds the cheapest Laptops in Germany across Amazon, eBay, and AliExpress. It clearly distinguishes from the sibling 'lookup_product' by focusing on searching multiple offers with filtering. The verb 'search' is specific and resource 'offers' is well-defined.

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?

The description provides explicit when-to-use scenarios: when a user asks for price, offer, 'cheap', 'where to buy', or a specific laptop. However, it does not mention when not to use or explicitly contrast with the sibling tool, leaving some ambiguity.

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.

  1. 2 tool updates
    • Changedlookup_product5 fields changed
      • 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)."
    • Changedsearch_offers11 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. 2 tool updates
    • First observedlookup_product
    • First observedsearch_offers

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.
    2
    MIT
  • A
    license
    Not graded
    quality
    F
    maintenance
    Enables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).
    16
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources