Skip to main content
Glama
Sign In

wospeicher.de Preisvergleich

by de.wospeicher
OverviewDiscussionsAdmin

Kaufberatung & Vergleiche auf wospeicher.de / buying guides

find_pages
Read-onlyIdempotent

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

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description usefully adds the return shape (title, summary, link), but says nothing about result limits, ranking, or what happens when the optional query is omitted, which is the main behavioural unknown left.

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 and the query examples are front-loaded, which is good. However the entire content is duplicated verbatim in German and English, roughly doubling length with no added information; one compact bilingual rendering would preserve the multilingual value with less waste.

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?

With no output schema, the description correctly states the returned fields, and it clarifies that all parameters are optional. It is still thin for a free-text search tool: no indication of result count, matching behaviour, or zero-result handling, which an agent needs to call it confidently.

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%, including the default/fallback logic for language (Accept-Language, else de, else en), so the schema already carries the parameter burden. The description only implies that query is a topic/question and adds no ranking or matching semantics beyond that; baseline 3 applies.

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 clear verb and resource (finds matching pages on wospeicher.de) and enumerates the page types it returns: comparisons, buying guides and brand pages. It does not explicitly name or contrast with the siblings lookup_product and search_offers, so an agent must infer the boundary from the topic examples.

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 phrasings ("welcher Stromspeicher ist gut fuer …", "worauf achten beim Kauf", "Modelle von <Marke>") in both languages, which makes the selection context clear. It stops short of explicit when-not-to-use guidance or pointing at lookup_product/search_offers for product-level or price-level queries.

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

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