Skip to main content
Glama
Sign In

wopool.de Preisvergleich

by de.wopool
OverviewDiscussionsAdmin

Kaufberatung & Vergleiche auf wopool.de / buying guides

find_pages
Read-onlyIdempotent

Findet die passenden Seiten auf wopool.de zu einer Frage rund um Pools: Vergleichsseiten (z.B. nach Ausstattung oder Preisklasse), Ratgeber/Kaufberatung und Markenseiten – jeweils mit Titel, Kurzbeschreibung und Link. Ideal fuer "welcher Pool ist gut fuer …", "worauf achten beim Kauf" oder "Modelle von ". EN: Finds matching pages on wopool.de – comparisons, buying guides and brand pages with title, summary and link. Use for "which Pool 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.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results include title, summary and link, and that the tool searches site pages rather than products or offers, which is helpful context beyond the annotations.

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 purpose is front-loaded and the structure is clear, but the German and English versions repeat the same content almost entirely. The bilingual duplication makes it longer than necessary for an agent that can read either 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?

For a two-parameter search tool with no output schema, the description provides enough context: what kinds of pages are returned and what fields each result contains. Annotations cover the safety profile, and schema covers parameters, so the remaining gaps are minor.

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 both the query and language parameters are already well documented. The description reinforces that the query is a topic or question and gives example query types, but it does not add language-specific behavior beyond the schema.

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?

The description states a specific verb and resource: it finds matching pages on wopool.de for pool-related questions, covering comparisons, buying guides and brand pages. It does not explicitly differentiate itself from the sibling tools lookup_product and search_offers, so it is clear but lacks direct sibling routing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful example queries such as 'welcher Pool ist gut fuer …' and 'Modelle von <Marke>', which implies appropriate usage. However, it does not explicitly say when to use this tool instead of lookup_product or search_offers, nor does it state exclusions.

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

All wopool.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