Skip to main content
Glama

getecoback-climate-weather

bosch_wth83v03_ablaufschlauch_nein_bezug

Read-only

Unterscheide beim WTH83V03 fehlenden Lieferumfang und nachgewiesene Anschlussmöglichkeit — Distinguish an omitted drain hose from documented drain capability

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wth83v03_bestaetigt": "<wth83v03_bestaetigt>",
      "haendler_nennt_zusatzschlauch": "<haendler_nennt_zusatzschlauch>",
      "anschluss_modellanleitung": "<anschluss_modellanleitung>",
      "ziel_ohne_tank": "<ziel_ohne_tank>"
    },
    "name": "bosch_wth83v03_ablaufschlauch_nein_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_ohne_tankYesEigene Nutzung setzt den Schlauch statt Tankentleerung voraus
wth83v03_bestaetigtYesExakte Bosch-Referenz WTH83V03 am konkreten Angebot bestätigt
anschluss_modellanleitungYesPassende Geräteanleitung bestätigt den tatsächlich gewünschten Ablaufschlaucheinsatz
haendler_nennt_zusatzschlauchYesAktuelles Angebot führt den Ablaufschlauch als zusätzlich enthalten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds no behavior beyond the topic: it does not say how conflicting inputs (e.g., 'offen' vs. 'ausgeschlossen') are resolved, whether a missing confirmation blocks a result, or what the returned determination looks like — and there is no output schema to compensate.

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?

A single front-loaded sentence pairs the German original with an English rendering and wastes no words. The bilingual duplication is slightly redundant but justified by the naming convention, and the key distinction appears in the first clause.

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

Completeness2/5

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

A four-required-parameter decision tool with no output schema needs the description to explain what a valid combination of inputs yields and how the three-state answers interact. Neither is addressed, so an agent knows the topic but not the semantics of a call or its result.

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% and each of the four parameters carries its own German explanation, including the two enums with belegt/ausgeschlossen/offen. The description adds no meaning beyond that, so the baseline of 3 applies; it neither compensates for nor degrades the schema.

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

Purpose3/5

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

The description names the model (WTH83V03) and the specific distinction it draws (omitted drain scope vs. documented drain capability), which is more precise than a generic label. However, the verb 'Unterscheide/distinguish' does not state what the tool actually produces — a verdict, a classification, a recommendation — so an agent cannot predict the outcome shape from the description alone.

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

Usage Guidelines2/5

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

There is no statement of when this tool should be used, when it should not, or which sibling handles adjacent cases. Given a catalog full of highly similar narrow decision tools, the absence of any routing hint leaves the agent to infer applicability from the model number alone.

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