Skip to main content
Glama

getecoback-raumklima

klima_fenster_nachtbetrieb_check

Read-only

Vor Nachtbetrieb prüfen, ob das Schlauchfenster in diesem Zustand geöffnet bleiben kann — Review night-time window constraints before running a hose AC.

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": {
      "fenster_offen": "<fenster_offen>",
      "sicherung_geprueft": "<sicherung_geprueft>",
      "fluchtweg_frei": "<fluchtweg_frei>"
    },
    "name": "klima_fenster_nachtbetrieb_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_offenYesFür den Betrieb muss das Fenster offen oder gekippt bleiben?
fluchtweg_freiYesVorgesehene Fluchtwege bleiben frei?
sicherung_geprueftYesDie Sicherheit der konkreten Öffnungsstellung wurde geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 and locality are covered. The description adds that this is a gating check on an existing state ('in diesem Zustand'), but says nothing about what the check returns, what a failed check implies, or what the caller should do next — relevant gaps since there is no output schema.

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?

Front-loaded with the timing condition and the core question, then a compact English gloss — no filler. The bilingual duplication is slightly redundant for a reader fluent in German, but it is a deliberate and small cost.

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 tool is simple (three required booleans, no nesting), but with no output schema the description should indicate the shape of the verdict the check produces; it does not. What is present is adequate to invoke the tool correctly, but not to interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each of the three booleans carries its own self-explanatory question, so the baseline would be 3. The description adds modest framing by tying the inputs to 'diesem Zustand' and to night-time operation, clarifying that the three answers jointly describe one snapshot rather than independent settings.

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?

States a specific verb ('prüfen' / check) and a specific resource/decision: whether the hose window may remain open in its current state before night operation. An agent can tell this is a pre-flight validation gate rather than a measurement or setup tool. It does not, however, name or contrast any sibling such as klima_abluftweg_pruefen.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Vor Nachtbetrieb' gives a clear triggering context for when to call the tool, and 'before running a hose AC' reinforces the ordering. No explicit when-not conditions or alternative tools are offered, which keeps it short of a 5.

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