F
license-
qualityB
maintenanceProvides real-time electricity prices, cheapest hours, and contract comparison for 40+ countries, enabling AI agents to make energy-aware decisions.
2
wosolar.de Preisvergleich
by de.wosolar
Server Details
Deutscher Preisvergleich für Solaranlagen & Balkonkraftwerke – Bestpreis-Suche (read-only).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.5/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have clearly distinct purposes: search_offers finds products based on search criteria, while lookup_product retrieves detailed price statistics and links for a specific product ID. There is no ambiguity or overlap.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern using lowercase with underscores (search_offers, lookup_product). The naming is predictable and clear.
Tool Count4/5
With only two tools, the server is slightly below the typical 3-15 range, but the pair covers the essential search-and-lookup workflow for a price comparison domain. Each tool earns its place, though a few more tools (e.g., for product categories or comparison) could be expected.
Completeness5/5
The tool surface covers the full lifecycle needed: users can search for products with filters and facets, then look up detailed price information for a specific product. There are no obvious gaps, and the workflow is complete for the stated purpose of price comparison.
Available Tools
2 toolslookup_productProdukt auf wosolar.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen wosolar.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 wosolar.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Produkt-ID: Amazon-ASIN oder externalId. | |
| url | No | Amazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| site | No | |
| count | Yes | |
| query | No | |
| facets | No | Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice. |
| products | Yes | |
| updatedAt | No | |
| disclosure | No | |
| catalogVersion | No |
Tool Definition Quality
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds that the tool is read-only (consistent with annotations) and describes the output data. Annotations already declare readOnlyHint and idempotentHint, so the description provides additional context on return values without contradicting annotations.
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 concise and front-loads the core purpose. It uses two short sentences in both German and English, which is slightly redundant but still efficient. No unnecessary details.
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 (not shown but mentioned), the description covers purpose, parameters, usage constraints, and return values adequately. It also references the sibling tool search_offers, making the context complete for an agent.
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?
While the input schema already has 100% coverage, the description adds crucial usage constraints (exactly one field) and clarifies the meaning of 'id' (link to externalId from search_offers) and 'url' (Amazon product URL with ASIN extraction), surpassing the schema's description.
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 that the tool looks up a specific product by ID or URL, specifies the returned data (best price, statistics, link), and distinguishes itself from the sibling tool search_offers by focusing on a single product lookup.
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 specifies that exactly one of 'id' or 'url' must be provided, and explains the sources for 'id' (ASIN or externalId from search_offers). While it doesn't explicitly state when not to use, the context (sibling tool) implies it's for specific lookup, not listing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offersSolaranlagen in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
Findet Solaranlagen zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wosolar.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Solaranlage 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 Solaranlagen across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | Auf eine Marke einschraenken (exakter Wert aus facets.marke, z.B. "Nike"). | |
| limit | No | Maximale Anzahl Ergebnisse (Default 24, max 100). | |
| query | No | Suchbegriff, z.B. Modell/Marke/Eigenschaft ("Balkonkraftwerk 800W", "iPhone 15 schwarz"). Optional. | |
| maxPrice | No | Hoechstpreis in EUR (optional). | |
| minPrice | No | Mindestpreis in EUR (optional). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| site | No | |
| count | Yes | |
| query | No | |
| facets | No | Verfuegbare Filter-Werte (Marke + domain-spezifische Attribute) mit Trefferzahlen — zum gezielten Nachfiltern via query/brand/minPrice/maxPrice. |
| products | Yes | |
| updatedAt | No | |
| disclosure | No | |
| catalogVersion | No |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and destructiveHint. The description adds behavioral details: it is read-only, returns price trends, and mentions affiliate links with unchanged prices. No contradictions, but could mention data freshness or rate limits.
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 front-loaded with purpose and usage, then details output. It is slightly verbose due to bilingual text, but every sentence adds information. It earns its place without unnecessary fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of searching with filters, the description covers inputs, outputs (including fields like priceStats, facets), and read-only nature. No output schema is provided, but the description fully explains return values, making it complete.
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% with descriptions, so baseline is 3. The description adds value by specifying default limit (24) and that brand must match facets exactly. It also explains the purpose of each parameter in context.
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 the tool finds the cheapest current price for solar products in Germany across Amazon, eBay, and AliExpress, using the verb 'Findet' and specifying the resource. It distinguishes itself from the sibling 'lookup_product' by focusing on search and 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 Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage guidance: 'Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Solaranlage fragt.' It clearly indicates when to use the tool and what queries it handles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Flicense-qualityBmaintenanceNine tools for indoor climate and household energy in Germany/EU: BTU sizing for a room, portable-AC window-seal length, live heatwave outlook, appliance running costs, heating watts, dew point for safe ventilation, and balcony-storage subsidy rules. Also searches and reads 133 guides on getecoback.com; no auth, no personal data, and every answer returns its source URL.
idealo MCP Serverofficial
Alicense-qualityFmaintenanceEnables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).14MIT- Alicense-qualityAmaintenance87+ specialized tools for German and European energy data. Direct AI access to Marktstammdatenregister (MaStR), ENTSO-E, Redispatch 2.0, and Grid Operations for utilities and datacenters.2GPL 3.0