A
licenseNot graded
qualityB
maintenanceEnables AI to search Geizhals price-comparison data, including products, best prices, price history, ratings, categories, and deals.
2
MIT
wopool.de Preisvergleich
by de.wopool
Server Details
Deutscher Preisvergleich für Pools – 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
Available Tools
2 toolslookup_productProdukt auf wopool.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen wopool.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 wopool.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 |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. The description adds that it returns best price, 30-day statistics, and offer link, which is beyond annotations. No contradictions.
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 contains both German and English versions of essentially the same information, leading to redundancy. It could be more concise by using one language.
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 low complexity (2 optional params, read-only) and presence of output schema, the description sufficiently covers what the tool does and returns. It is complete enough for an agent to use correctly.
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 parameter descriptions. The description adds the constraint 'exactly one of the fields' and clarifies the types of IDs (ASIN/externalId), adding value over schema.
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 verb 'looks up' and the specific resource 'product in the wopool.de catalog', and distinguishes it from the sibling 'search_offers' by specifying it is for a concrete product.
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 explicitly requires exactly one of 'id' or 'url', and the context of 'concrete product' implies when to use vs. the sibling for multiple offers. No explicit when-not-to-use mention, but adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offerspool in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
Findet pool zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wopool.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten pool 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 pool 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 |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint, destructiveHint false, idempotentHint true. The description adds that the tool is read-only and mentions affiliate links and that the price is unchanged. No contradictions; description enriches behavioral context beyond 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 front-loaded with the main purpose and includes necessary details. It is moderately concise, though it mixes languages and could be slightly shorter without losing value.
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?
The description explains output fields in detail (title, best price, brand, image, price trend, attributes, links, facets). Given the presence of an output schema, the description fully covers what the tool returns and how to use filters, making it complete.
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%, so baseline is 3. The description mentions filterable fields (query, brand, price range) and facets for refinement, but does not add new meaning beyond what the schema already provides for each parameter.
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's purpose: to find the cheapest current price in Germany for 'pool' across Amazon, eBay, and AliExpress, with price comparison. It distinguishes from the sibling 'lookup_product' by focusing on price search versus 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?
The description explicitly instructs when to use the tool: when a user asks about price, offer, cheap, where to buy, or a specific pool. However, it does not provide explicit 'when not to use' guidance or mention alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Deutscher Preisvergleich für Grills – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Handys – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Tablets – Bestpreis-Suche (read-only).
Deutscher Preisvergleich für Stromspeicher – Bestpreis-Suche (read-only).
Related MCP Servers
idealo MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables product search, price comparison, and price history analysis across 6 European marketplaces (DE, AT, GB, FR, IT, ES).15MIT- AlicenseAqualityBmaintenanceEnables searching geizhals.de for products and retrieving shop prices and offers to assist with price comparison.2MIT
- FlicenseNot gradedqualityDmaintenanceDTC competitor intelligence: catalog snapshots, price history, cross-brand product comparison, and drop/restock detection for 84 Shopify-powered brands. Pay-per-call via Apify.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation2/5
Both tools deal with product lookup and return similar information (best price, 30-day trend, links). An agent may find it unclear whether to use 'search_offers' for a specific ID or 'lookup_product' for a broad search, as the descriptions indicate overlap.
Naming Consistency5/5
Both tool names follow a consistent verb_noun pattern: 'lookup_product' and 'search_offers'. The naming is clear and predictable.
Tool Count3/5
With only 2 tools, the server is minimal. While it covers search and specific lookup, a price comparison service typically benefits from additional tools (e.g., category browsing, product comparison). The count feels slightly thin.
Completeness4/5
The tools cover the core use cases of searching for the cheapest price and looking up a specific product with price trends. Minor gaps exist, such as a lack of tools for browsing categories or viewing full price history beyond 30 days, but the surface is largely complete for a focused service.