Skip to main content
Glama

wohandy.de Preisvergleich

Look up one partner offer on wohandy.de

lookup_product
Read-onlyIdempotent

Returns the current price and links of ONE partner offer that search_offers returned before. USE WHEN you need to re-check the price of an offer from an earlier search_offers result. Do not use it to search – use search_offers. PARAMETERS: "id" = externalId from search_offers, or "url" = the product URL. EXAMPLE: {"id":""}. RETURNS: the same structure as search_offers with at most one entry in products[] (empty if the offer is gone).

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": "lookup_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOffer ID: externalId from search_offers.
urlNoAlternatively the product URL (optional).
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".

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. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Produkt-ID / product ID (externalId aus search_offers)."New value: +"Offer ID: externalId from search_offers."
    • 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 / url / description
      Previous value: -"Alternativ eine Produkt-URL / product URL (optional)."New value: +"Alternatively the product URL (optional)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Produkt-ID: Amazon-ASIN oder externalId."New value: +"Produkt-ID / product ID (externalId aus search_offers)."
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "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.",
      +  "enum": [
      +    "de",
      +    "en",
      +    "tr",
      +    "ar",
      +    "ru",
      +    "pl",
      +    "uk",
      +    "fr",
      +    "es",
      +    "it",
      +    "pt",
      +    "nl",
      +    "ro",
      +    "el",
      +    "hr",
      +    "cs",
      +    "hu",
      +    "fa",
      +    "zh",
      +    "ja"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"Amazon-Produkt-URL (z.B. https://www.amazon.de/dp/B0ABC123DE) — die ASIN wird extrahiert."New value: +"Alternativ eine Produkt-URL / product URL (optional)."
  3. Changed5 schema fields changed
    • 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)."
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: at most one entry is returned and products[] is empty when the offer is gone, which tells the agent how to detect a stale offer. The only gap is that the return-shape note partially duplicates the existing output schema.

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 short, front-loaded with purpose, and organized into labeled USE WHEN / Do not / PARAMETERS / EXAMPLE / RETURNS sections. The RETURNS sentence is somewhat redundant with the existing output schema, but it is brief enough to justify its place for chaining decisions.

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 simple, read-only single-lookup tool with full annotation coverage, a 100%-covered schema and an output schema, this covers everything an agent needs: purpose, trigger, exclusion, the id-or-url choice, an example, and the empty-result case. Nothing required to invoke it correctly 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 description coverage is 100%, so the baseline is 3, but the description earns above baseline by stating the id/url either-or relationship (externalId from search_offers versus the product URL) and giving a concrete call example {"id":"<externalId>"}. It does not describe the language parameter, but the schema already covers that in full.

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 names a concrete verb and resource — returns the current price and links of exactly ONE partner offer — and immediately scopes it as operating on an offer from an earlier search_offers result. An agent can distinguish it from search_offers and find_pages without opening any schema.

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?

It gives an explicit positive trigger ("USE WHEN you need to re-check the price of an offer from an earlier search_offers result") and an explicit exclusion plus redirect ("Do not use it to search – use search_offers"). Nothing about when to pick this tool is left to inference.

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