Skip to main content
Glama

getecoback-raumklima

philips_hd9945_originalteile_und_fremdteile_pflege

Read-only

Bei gemischtem Backset sicher belegte Originalteile von Ersatzformen ohne eigene Pflegeangabe abgrenzen — Keep the documented dishwasher claim attached to identified kit components.

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": {
      "hd9945_01_belegt": "<hd9945_01_belegt>",
      "originale_backform": "<originale_backform>",
      "originale_foermchen": "<originale_foermchen>",
      "andere_foermchen": "<andere_foermchen>",
      "andere_eigene_pflegeangabe": "<andere_eigene_pflegeangabe>"
    },
    "name": "philips_hd9945_originalteile_und_fremdteile_pflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
andere_foermchenYesSeparat vorhandene Silikonförmchen ohne belegte Zuordnung zum Originalkit.
hd9945_01_belegtYesIst die genau betrachtete Originalausführung HD9945/01 belegt?
originale_backformYesZustand der Herkunftszuordnung der vorhandenen Back- und Auflaufform.
originale_foermchenYesEindeutig zum Originalkit zugeordnete Silikonförmchen.
andere_eigene_pflegeangabeYesDavon durch ihre eigenen Unterlagen bestätigte Förmchen für dieselbe Reinigungsart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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; the description adds only an abstract rule about keeping a dishwasher claim attached. It does not say what the tool returns, how conflicting inputs (e.g. originale_backform='abweichend' combined with non-zero originale_foermchen) are resolved, or whether the output is a count, a boolean, or a verdict.

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 definition is short and front-loads the scenario, but the German sentence and the English gloss are not parallel — the English introduces a different framing ('dishwasher claim') rather than translating — which adds ambiguity instead of clarity. Nothing is padded, but the two clauses do not converge on one crisp statement.

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?

With five required parameters, no output schema, and a genuinely intricate evidence-tracking domain (original kit vs. substitute molds vs. own care documentation), the description leaves far too much unexplained: no return semantics, no counting logic, no handling of the 'offen' enum case. An agent could not reliably invoke this tool from the definition alone.

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% with self-explanatory German field descriptions and an enum, so the schema carries the parameter burden. The description adds no extra meaning about how the five fields interact (e.g. that andere_eigene_pflegeangabe is a subset of andere_foermchen), so the baseline of 3 applies.

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 frames the scenario ('Bei gemischtem Backset') and the aim ('belegte Originalteile von Ersatzformen ohne eigene Pflegeangabe abgrenzen', 'Keep the documented dishwasher claim attached to identified kit components'), so the domain topic is inferable. But it never states a clear operation — no verb like compute/check/return — so an agent cannot confidently predict what the tool produces from the five inputs.

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?

A single conditional context ('bei gemischtem Backset') hints at when the tool applies, but there is no comparison to any sibling, no statement of when not to use it, and no prerequisites such as which evidence counts as 'belegt'. The agent must guess its place among the many similarly named Philips/pflege tools.

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