Skip to main content
Glama

wosolar.de Preisvergleich

Compare prices on wosolar.de (Solaranlagen)

search_offers
Read-onlyIdempotent

Price comparison for the German market (EUR): today's best prices for Solaranlagen from many shops (incl. Amazon and eBay) on wosolar.de. USE WHEN the user asks for a price, a deal, "cheapest", "where to buy" or a specific product of this category (Solaranlage). PARAMETERS: "query" = model, brand or feature; optional "brand" (exact value from facets), "minPrice"/"maxPrice" in EUR, "limit". EXAMPLES: {"query":"Balkonkraftwerk 800 W"} · {"query":"Balkonkraftwerk mit Speicher","maxPrice":500} · {"brand":"","maxPrice":100,"language":"en"}. RETURNS: siteSearchUrl (result list for the query on wosolar.de with the current prices of ALL shops – works on mobile; this is the link to give the user), products[] (partner offers that may be passed on: title, price, merchant, priceUpdatedAt, url = tracked shop link, detailUrl = product page with all shop prices; may be empty), browse (matching comparison pages, buying guides, brand pages) and facets for refining. Give links to the user UNCHANGED (tracked affiliate links, same price for the buyer). If products is empty, send the user to siteSearchUrl. Set "language" to the user's language.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand, exact value from facets (id "marke"), e.g. "Nike" (optional).
limitNoMaximum number of partner offers (default 24, max 100).
queryNoSearch term: model, brand or feature, e.g. "Balkonkraftwerk 800 W". Optional (without it: popular offers).
languageNoLanguage of the linked pages (ISO 639-1, e.g. "de", "en", "tr", "ar", "fr"). Set it to the user's language. Default: Accept-Language header, otherwise "de"; unsupported languages fall back to "en".
maxPriceNoMaximum price in EUR (optional).
minPriceNoMinimum price in EUR (optional).

Output 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. Changed6 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Marke / brand (exakter Wert aus facets.marke, z.B. \"Nike\")."New value: +"Brand, exact value from facets (id \"marke\"), e.g. \"Nike\" (optional)."
    • changedInput schema / properties / language / description
      Previous value: -"Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en."New value: +"Language of the linked pages (ISO 639-1, e.g. \"de\", \"en\", \"tr\", \"ar\", \"fr\"). Set it to the user's language. Default: Accept-Language header, otherwise \"de\"; unsupported languages fall back to \"en\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximale Anzahl Partner-Angebote (Default 24, max 100)."New value: +"Maximum number of partner offers (default 24, max 100)."
    • changedInput schema / properties / maxPrice / description
      Previous value: -"Hoechstpreis / max price in EUR (optional)."New value: +"Maximum price in EUR (optional)."
    • changedInput schema / properties / minPrice / description
      Previous value: -"Mindestpreis / min price in EUR (optional)."New value: +"Minimum price in EUR (optional)."
    • changedInput schema / properties / query / description
      Previous value: -"Suchbegriff / search term, z.B. Modell, Marke, Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15\"). Optional."New value: +"Search term: model, brand or feature, e.g. \"Balkonkraftwerk 800 W\". Optional (without it: popular offers)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Antwortsprache / response language (de|en). Default: Accept-Language, sonst de."New value: +"Sprache der Seiten-Links / language of page links (ISO 639-1, z. B. de, en, tr, ar, fr, zh). Default: Accept-Language, sonst de. Bietet die Seite die Sprache nicht an: en."
    • changedInput schema / properties / language / enum
      Previous value: -[
      -  "de",
      -  "en"
      -]New value: +[
      +  "de",
      +  "en",
      +  "tr",
      +  "ar",
      +  "ru",
      +  "pl",
      +  "uk",
      +  "fr",
      +  "es",
      +  "it",
      +  "pt",
      +  "nl",
      +  "ro",
      +  "el",
      +  "hr",
      +  "cs",
      +  "hu",
      +  "fa",
      +  "zh",
      +  "ja"
      +]
  3. Changed6 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. \"Nike\")."New value: +"Marke / brand (exakter Wert aus facets.marke, z.B. \"Nike\")."
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Antwortsprache / response language (de|en). Default: Accept-Language, sonst de.",
      +  "enum": [
      +    "de",
      +    "en"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximale Anzahl Ergebnisse (Default 24, max 100)."New value: +"Maximale Anzahl Partner-Angebote (Default 24, max 100)."
    • changedInput schema / properties / maxPrice / description
      Previous value: -"Hoechstpreis in EUR (optional)."New value: +"Hoechstpreis / max price in EUR (optional)."
    • changedInput schema / properties / minPrice / description
      Previous value: -"Mindestpreis in EUR (optional)."New value: +"Mindestpreis / min price in EUR (optional)."
    • changedInput schema / properties / query / description
      Previous value: -"Suchbegriff, z.B. Modell/Marke/Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15 schwarz\"). Optional."New value: +"Suchbegriff / search term, z.B. Modell, Marke, Eigenschaft (\"Balkonkraftwerk 800W\", \"iPhone 15\"). Optional."
  4. 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)."
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses that products[] may be empty, that url is a tracked affiliate link that must be passed through unchanged, that siteSearchUrl covers ALL shops and works on mobile, and what detailUrl/browse/facets contain. The affiliate-link pass-through constraint is exactly the kind of operational detail annotations cannot express.

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?

Front-loaded with purpose, then labeled PARAMETERS / EXAMPLES / RETURNS blocks, which is easy to scan. It is somewhat long and repeats the language instruction twice (once under PARAMETERS, once as a closing sentence), and the RETURNS section partly restates the output schema.

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?

For a zero-required-parameter search tool with an output schema, this covers everything an agent needs: when to call it, what each parameter means, worked examples, what comes back, and how to handle the empty-partner-offers case. Nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra by explaining query as model/brand/feature, telling the agent brand must be an exact value from facets (id 'marke'), and repeating the language-matching rule. The three concrete example payloads add invocation guidance the schema alone does not provide.

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?

States a specific verb and resource: price comparison for Solaranlagen on wosolar.de in EUR, including shop coverage (Amazon, eBay). It is precise enough to distinguish from a generic page lookup, but it never names the siblings find_pages or lookup_product or explains how this differs from them, so an agent must infer the boundary.

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?

Gives an explicit USE WHEN trigger list ('price', 'deal', 'cheapest', 'where to buy', specific product of this category) plus a fallback rule (if products is empty, send the user to siteSearchUrl). It stops short of naming an alternative tool or a when-not condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources