Skip to main content
Glama

getecoback-climate-weather

klima_selbstverdunstung_modusbereich

Read-only

Unterscheide Selbstverdunstung im Kühlbetrieb und den dokumentierten Ablauf beim Entfeuchten — Distinguish cooling evaporation from drainage in dry mode

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": {
      "einsatz": "<einsatz>",
      "selbstverdunstung_kuehlen": "<selbstverdunstung_kuehlen>",
      "ablauf_entfeuchten": "<ablauf_entfeuchten>",
      "dauerlauf_geplant": "<dauerlauf_geplant>"
    },
    "name": "klima_selbstverdunstung_modusbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
einsatzYesVorgesehener Betrieb
dauerlauf_geplantYesLängerer Betrieb ohne regelmäßiges Tankleeren geplant
ablauf_entfeuchtenYesAblauf ausdrücklich für den Entfeuchtungsmodus
selbstverdunstung_kuehlenYesSelbstverdunstung ausdrücklich für den Kühlmodus

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 the safety profile is covered by structured data. The description adds essentially nothing beyond the topic — no indication of what is returned, how the enum values are combined, or what happens when a parameter is "offen".

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?

It is short and front-loaded, but the second half is a literal English translation of the first rather than new information, so half the text does not add value. No wasted length, though little structural guidance.

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?

For a read-only tool with four required enum inputs and no output schema, the description should clarify what determination the inputs produce. It leaves the agent guessing how to interpret a result, which is a meaningful gap for a decision-style tool.

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 all four parameters carry German descriptions plus three enums, so the schema does the heavy lifting and the baseline is 3. The description mentions the cooling/drainage distinction but does not explain how einsatz, selbstverdunstung_kuehlen, ablauf_entfeuchten and dauerlauf_geplant interact.

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 a specific domain object (self-evaporation in cooling vs. documented drainage in dehumidify mode) and a verb of sorts ("Unterscheide"), so the topical scope is clear. But it never says what the tool actually does operationally — classify a case, validate a combination of the four inputs, or return a determination — so an agent cannot fully predict the effect of calling it.

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 to call this versus the many sibling klima tools, nor any prerequisite or exclusion. The only implicit cue is the cooling/dry-mode framing, which an agent must infer on its own.

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