Skip to main content
Glama

getecoback-raumklima

luftbefeuchter_betrieb_nach_routinewechsel

Read-only

Ermitteln, ob ein laut Anleitung austauschbarer und geeigneter Vorratstank zwischen zwei Sitzungen tatsächlich einen Pflegeengpass löst. — Compare a normally cleaned tank with an existing, approved ready tank at the next session.

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": {
      "bisheriger_tank_frei_ab_min": "<bisheriger_tank_frei_ab_min>",
      "ersatztank_frei_ab_min": "<ersatztank_frei_ab_min>",
      "start_ziel_min": "<start_ziel_min>",
      "ersatz_bestaetigt": "<ersatz_bestaetigt>"
    },
    "name": "luftbefeuchter_betrieb_nach_routinewechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_ziel_minYesGewünschter Start der nächsten Sitzung auf derselben Minutenachse.
ersatz_bestaetigtYesEigenes Modell, verwendeter Ersatz und alle weiteren Schritte sind für diesen Wechsel freigegeben.
ersatztank_frei_ab_minYesEntsprechender Zeitpunkt beim bereits vorhandenen geeigneten Ersatz.
bisheriger_tank_frei_ab_minYesZeitpunkt nach der vollständigen vorgeschriebenen Routine beim verwendeten Tank.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds that this is a verdict-producing comparison ('ob ... tatsächlich ... löst'), which tells the agent it is evaluating rather than mutating state. However, it does not say what the verdict looks like or how the two timestamps are weighed against the target start.

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 core statement is front-loaded in the first sentence, but the second sentence is essentially a shortened English restatement rather than new information. The German sentence is also long and jargon-heavy ('laut Anleitung austauschbarer und geeigneter Vorratstank'), which costs clarity without adding precision.

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

Completeness4/5

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

For a four-parameter, read-only evaluation tool with no output schema, the definition supplies the decision context, the two comparison points, and the approval gate, while annotations cover the safety profile. The main remaining gap is the absence of any hint about the shape of the result, which matters for a tool whose whole output is a verdict.

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%, so the four parameters are already fully documented, and the baseline is 3. The description adds only the framing that bisheriger_tank_frei_ab_min and ersatztank_frei_ab_min are the two sides of the comparison; it gives no extra meaning for start_ziel_min or the ersatz_bestaetigt gate beyond what the schema states.

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?

The description names a specific operation — determining whether an approved reserve tank actually resolves a maintenance bottleneck between two sessions — and frames it as a comparison between the routine-cleaned tank and the ready replacement. That is more than a restatement of the name. It stops short of a 5 because it never distinguishes this evaluation from nearby siblings such as luftbefeuchter_lokale_regelung_ersatzroutine or luftbefeuchter_zweistufen_tank_restmenge.

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?

The only contextual cue is that the comparison happens 'at the next session' after a routine change. There is no statement of prerequisites, no when-not-to-use condition, and no named alternative for the case where no approved replacement exists. An agent must infer the triggering situation entirely from the name and parameters.

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