Skip to main content
Glama
Sign In

wokonsole.de Preisvergleich

by de.wokonsole
OverviewDiscussionsAdmin

Kaufberatung & Vergleiche auf wokonsole.de / buying guides

find_pages
Read-onlyIdempotent

Findet die passenden Seiten auf wokonsole.de zu einer Frage rund um Spielekonsolen: Vergleichsseiten (z.B. nach Ausstattung oder Preisklasse), Ratgeber/Kaufberatung und Markenseiten – jeweils mit Titel, Kurzbeschreibung und Link. Ideal fuer "welcher Spielekonsole ist gut fuer …", "worauf achten beim Kauf" oder "Modelle von ". EN: Finds matching pages on wokonsole.de – comparisons, buying guides and brand pages with title, summary and link. Use for "which Spielekonsole should I buy", "what to look for" or brand questions.

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

Input Schema

NameRequiredDescriptionDefault
queryNoThema oder Frage / topic or question (optional).
languageNoSprache 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Antwortsprache / response language (de|en). Default: Accept-Language, sonst de."New 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."
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "de",
-  "en"
-]New value: +[
+  "de",
+  "en",
+  "tr",
+  "ar",
+  "ru",
+  "pl",
+  "uk",
+  "fr",
+  "es",
+  "it",
+  "pt",
+  "nl",
+  "ro",
+  "el",
+  "hr",
+  "cs",
+  "hu",
+  "fa",
+  "zh",
+  "ja"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description's job is to add context — and it does, naming the three returned fields and confirming the search is scoped to wokonsole.de only. It omits result-count limits, ranking order, and what an empty query returns, which are real behavioral gaps given both parameters are optional.

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 German half is front-loaded and information-dense, but the English half is a near-verbatim restatement that roughly doubles length without adding facts. Bilingualism is defensible for a 20-language tool, yet the duplication still dilutes conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return fields are described, which offsets the missing output schema, and annotations carry the safety story. However, with zero required parameters the description never explains what a call with no query yields (all pages? error?), leaving a meaningful hole for a two-optional-param tool.

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 coverage is 100%, so both parameters are fully documented in the schema and the baseline is 3. The description adds query examples ('Modelle von <Marke>') that hint at acceptable input shape, but says nothing about the language parameter or its fallback behavior beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Findet die passenden Seiten auf wokonsole.de') and enumerates the page types returned (Vergleichsseiten, Ratgeber/Kaufberatung, Markenseiten). It implicitly separates itself from lookup_product/search_offers by framing results as editorial pages with title/summary/link, but never names those siblings explicitly.

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?

Gives concrete trigger phrases ('welcher Spielekonsole ist gut fuer …', 'worauf achten beim Kauf', 'Modelle von <Marke>') that map cleanly onto the tool's purpose. It stops short of saying when NOT to use it or pointing to lookup_product/search_offers for product- or offer-level questions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All wokonsole.de Preisvergleich toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources