wokonsole.de Preisvergleich
Server Details
Deutscher Preisvergleich für Spielekonsolen – 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.2/5 across 2 of 2 tools scored.
The two tools have clearly distinct purposes: search_offers finds consoles by criteria, while lookup_product retrieves details for a specific product by ID or URL. There is no overlap in functionality.
Both tools follow a consistent verb_noun pattern using snake_case: lookup_product and search_offers. The naming is predictable and clear.
With only 2 tools, the server feels minimal for a price comparison domain. While the tools cover search and detail lookup, additional tools like listing categories or comparing multiple products would round out the set.
The server covers the core functions of searching and looking up product details, but lacks tools for broader catalog browsing, price history beyond 30 days, or cross-product comparison. Minor gaps exist.
Available Tools
2 toolslookup_productProdukt auf wokonsole.de per ID/URL nachschlagenARead-onlyIdempotentInspect
Schlaegt ein konkretes Produkt im aktuellen wokonsole.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 wokonsole.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 already declare readOnlyHint, idempotentHint, destructiveHint. Description adds return value details and ASIN extraction from URL, providing complementary 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, effectively front-loaded with German and English. Could be slightly more concise by dropping bilingual repetition, but it's well-structured.
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 presence of output schema, full parameter coverage, annotations, and sibling tool mention, the description is complete and adds essential behavior and return value context.
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. Description clarifies that 'id' can be ASIN or externalId from search_offers, and 'url' is an Amazon product URL from which ASIN is extracted, adding meaningful context.
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?
Clear verb 'lookup' and specific resource 'product' with scope 'by ID or URL' and includes return values (best price, statistics, link). Distinguishes from sibling 'search_offers' which likely searches 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?
States requirement 'exactly one of id/url' and notes read-only behavior. Could explicitly mention when to use lookup vs search_offers, but the distinction is implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_offersSpielekonsolen in Deutschland zum Bestpreis finden (Amazon, eBay, AliExpress)ARead-onlyIdempotentInspect
Findet Spielekonsolen zum guenstigsten aktuellen Preis in Deutschland (EUR) ueber Amazon, eBay und AliExpress — Preisvergleich wokonsole.de. Nutze dieses Tool, wenn ein Nutzer nach Preis, Angebot, "guenstig", "wo kaufen" oder einem konkreten Spielekonsole 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 Spielekonsolen 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 already indicate read-only, idempotent, non-destructive. The description adds context about affiliate links, price unchanged, and response details (facets, price trend). 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is somewhat lengthy due to bilingual content (German and English). It front-loads the purpose but could be more concise. Every sentence adds value, but overall slightly verbose.
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?
With annotations, output schema, and 5 parameters all documented, the description covers the tool's behavior, response structure, and usage context well. It mentions facets, price trend, and direct links, making it complete.
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% with detailed descriptions. The description adds minimal extra meaning, mainly mentioning filterability by search term, brand, and price range. It does not significantly enhance understanding beyond the 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 Spielekonsolen in Germany across Amazon, eBay, and AliExpress. It uses specific verbs ('Findet') and resources, and distinguishes from the sibling tool 'lookup_product' by focusing on search/offers.
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?
Explicitly states when to use the tool: when a user asks about price, offer, 'cheap', 'where to buy', or a specific console. It does not explicitly state when not to use it, but the guidance is clear and helpful.
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!