Skip to main content
Glama

getecoback-climate-weather

philips_azur_calc_pflegefenster_kalender_und_anlass

Read-only

Für den DST7040 das empfohlene Kalenderintervall getrennt von dokumentierten braunen Flecken oder braunem Wasser prüfen — Separate the manual’s calendar maintenance range from an observed trigger.

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": {
      "dst7040_belegt": "<dst7040_belegt>",
      "vollmonate_seit_calc": "<vollmonate_seit_calc>",
      "datum_belegt": "<datum_belegt>",
      "hart": "<hart>",
      "braun": "<braun>"
    },
    "name": "philips_azur_calc_pflegefenster_kalender_und_anlass"
  }
}

Input Schema

NameRequiredDescriptionDefault
hartYesIst hartes Wasser vor Ort belegt?
braunYesEigenes Protokoll von braunen Flecken oder braunem Wasser.
datum_belegtYesIst der letzte Vorgang datiert und dem gleichen Exemplar zugeordnet?
dst7040_belegtYesIst genau DST7040 in der zum Gerät gehörigen Ausgabe identifiziert?
vollmonate_seit_calcYesVollständig verstrichene Kalendermonate seit eindeutig protokollierter letzter Calc-Pflege.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 the conceptual behavior that manual specifications and personal observations are kept apart, but it does not say what verdict is produced (e.g., 'within/outside interval' or 'evidence insufficient') for a decision-type tool.

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?

One compact sentence with the device front-loaded, followed by an English gloss. The German/English duplication is mild redundancy but serves disambiguation, and no sentence is filler.

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?

For a tool with five all-required parameters, an output-less design, and a comparison-based decision, the description is thin on what the outcome means and how the confirmed/discrepant/open enum values influence it. Annotations cover the read-only profile, but the decision semantics an agent needs to interpret results are only sketched.

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 all five required parameters, enum values, and bounds documented inline, so the baseline is 3. The description only loosely maps 'braune Flecken oder braunes Wasser' to the braun field and 'Kalenderintervall' to vollmonate_seit_calc; it adds no new semantics such as how the Belegt-Flags gate the result.

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?

Names a concrete device (DST7040) and a concrete resource (empfohlenes Kalenderintervall / Calc-Pflegefenster), and states the core operation: comparing the manual's calendar maintenance range against an observed trigger. It is distinguishable from observation-only siblings, though the verb 'prüfen' leaves what the check actually returns implicit.

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?

The 'getrennt von' phrasing implies the use case: invoke this when a documented brown-spot/brown-water observation exists and you must not conflate it with the manual's calendar interval. However, no explicit when-not condition or named alternative among the many Philips Azur siblings is given.

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