Skip to main content
Glama

getecoback-raumklima

dunstabzug_dkf12r_regeneration_und_gesamtalter

Read-only

Führe beim DKF 12-R Regenerationsabstand und Gesamtalter getrennt weiter — Keep regeneration timing separate from total service age for DKF 12-R

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": {
      "materialnummer_10271450": "<materialnummer_10271450>",
      "einbau_monat": "<einbau_monat>",
      "regeneration_monat": "<regeneration_monat>",
      "auswertung_monat": "<auswertung_monat>",
      "zeiten_und_teil_bestaetigt": "<zeiten_und_teil_bestaetigt>"
    },
    "name": "dunstabzug_dkf12r_regeneration_und_gesamtalter"
  }
}

Input Schema

NameRequiredDescriptionDefault
einbau_monatYesMonat der Erstinbetriebnahme im eigenen fortlaufenden Zeitraum
auswertung_monatYesAuswertungszeitpunkt auf derselben Zeitskala
regeneration_monatYesMonat der zuletzt dokumentierten Regeneration, bei keiner wie Erstinbetriebnahme
materialnummer_10271450YesExakter Miele DKF 12-R, Materialnummer 10271450, bestätigt
zeiten_und_teil_bestaetigtYesAlle Zeitangaben gehören zu demselben physischen Filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already disclose readOnlyHint=true and openWorldHint=false; the description adds only the domain rule that regeneration timing is kept separate from total age. It does not state whether 'weiterführen' means calculation versus persistence, nor what is validated or returned.

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?

The definition is a single core sentence repeated in English, so it is front-loaded and easy to scan. The bilingual repetition is mildly redundant but useful for clarity.

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?

The fully described schema and read-only annotation cover most invocation needs, but with no output schema the description should explain what the separate-tracking operation returns or validates. The missing result behavior leaves a moderate gap.

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 coverage is 100%, and all five parameters carry descriptive text explaining installation, regeneration, evaluation months, and the confirmations. The description adds no parameter-level meaning beyond the general separation rule, so the baseline score 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 names the DKF 12-R and the two quantities, regeneration interval and total service age, but the verb 'weiterführen' leaves unclear whether the tool computes, validates, or records them. It does not distinguish this purpose from the many sibling Dunstabzug tools.

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?

It supplies no when-to-use condition, no when-not-to-use condition, and no sibling alternative. An agent only learns that the tool concerns DKF 12-R, not when it should be selected over related filter or care 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