Skip to main content
Glama

wohandy.de Preisvergleich

by de.wohandy
OverviewDiscussionsAdmin

Handys in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)

search_offers
Read-onlyIdempotent

Findet Handys zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wohandy.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Handy 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 Handys 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.3/5.0
Behavior5/5

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

Annotations already mark it read-only/idempotent/non-destructive, and the description adds substantial context: full-catalog search over hundreds of products, 30-day price-trend field semantics (priceStats.isLowest30d), facet refinement, direct purchase links, and affiliate disclosure with unchanged price. No contradiction 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.

Conciseness3/5

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

The German portion is well front-loaded and information-dense, but the English sentence at the end largely repeats the German opening and result summary. This duplication prevents the description from being maximally 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 optional parameters, existing output schema, and read-only annotations, the description covers when to use, what is searched, what is returned, how to refine via facets, and the affiliate behavior. Nothing material is missing for an agent to select and invoke the tool correctly.

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%, and the schema already defines query, brand, minPrice, maxPrice, and limit precisely. The description adds only a general 'filterbar per Suchbegriff, Marke und Preisspanne' mapping, which is useful but does not go beyond the schema baseline.

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 opens with a specific verb+resource ('Findet Handys zum guenstigsten aktuellen Preis in Deutschland') and defines geographic scope, marketplace coverage, and result semantics. It positions this as a catalog-wide price search tool with filters, which implicitly differentiates it from the sibling lookup_product for exact product lookups.

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 gives explicit invocation triggers ('Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, guenstig, wo kaufen oder einem konkreten Handy fragt'). It does not name when-not-to-use conditions or explicitly route to lookup_product, so it falls just short of the fullest guidance.

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

All wohandy.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