wohandy.de Preisvergleich
Server Details
Deutscher Preisvergleich für Handys – 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.
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.
Tool Definition Quality
Average 4.6/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes. 'search_offers' finds products based on search criteria, while 'lookup_product' retrieves details for a specific product by ID or URL. No overlap.
Both tools use consistent snake_case naming convention ('lookup_product', 'search_offers'), following a clear verb_noun pattern.
The server has only two tools, but they cover the core functionality of searching and looking up products. While minimal, it is appropriate for a focused price comparison server.
The tool surface is complete for the server's read-only purpose: search for products and look up details. No obvious missing operations given the domain.
Available Tools
2 toolslookup_productProdukt auf wohandy.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen wohandy.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 wohandy.de catalog by ID (ASIN/externalId) or Amazon product URL (read-only).
| 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
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description confirms 'read-only' and adds detail about returned data (best price, statistics, link), providing complete behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, two sentences, front-loading key information in German and English. Every sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 fully covers purpose, parameter constraints, and return value highlights. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers both parameters with descriptions (100% coverage). Description adds critical constraint that exactly one must be provided and clarifies that URL is an Amazon product link with ASIN extraction.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool looks up a specific product by ID or URL and returns best price, 30-day statistics, and offer link. It distinguishes from the sibling tool 'search_offers' which is for searching multiple products.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 to be provided. It implies usage when a specific product identifier is known, but could be more explicit about when not to use it vs. search_offers.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offersHandys in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
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 ~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 Handys across Amazon, eBay and AliExpress; returns best price, price trend, filter attributes and a direct link.
| 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
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnly, idempotent, non-destructive. The description adds detail: searches ~150 products, returns specific fields (title, best price, brand, image, 30-day trend, attributes, direct purchase link, detailUrl, facets) and mentions affiliate nature with unchanged price.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with purpose but includes both German and English texts, which is redundant. It could be more concise by removing one language version.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema existence, the description provides complete context: explains return fields (title, best price, brand, image, price trend, attributes, links, facets) and search behavior, making it sufficiently informative for correct tool selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, baseline 3. The description adds context: brand is exact match from facets.marke, and gives example for query parameter. It also explains filters for price range and maximum results beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds the cheapest current price for Handys in Germany across Amazon, eBay, and AliExpress. It distinguishes from the sibling tool 'lookup_product' by focusing on price comparison and search.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says use when user asks about price, offer, 'cheap', 'where to buy', or a specific phone. It provides clear context but does not explicitly exclude use cases or compare with 'lookup_product'.
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!