Skip to main content
Glama

getecoback-raumklima

klima_zu_und_rueckluft_messen

Read-only

Gemessene Temperaturspreizung zwischen Ansaug- und Ausblasluft im Kühlbetrieb einordnen — Estimate supply-to-return temperature difference from paired AC readings.

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": {
      "rueckluft_c": "<rueckluft_c>",
      "zuluft_c": "<zuluft_c>",
      "fehler_je_c": "<fehler_je_c>",
      "stabiler_kuehlmodus": "<stabiler_kuehlmodus>"
    },
    "name": "klima_zu_und_rueckluft_messen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuluft_cYesZeitgleich gemessene Ausblasluft in °C. Messfühler außen halten.
fehler_je_cYesAbsoluter Fehler je Messung in °C.
rueckluft_cYesLuft vor dem Ansaugpunkt in °C, nicht die Raumtemperatur anderswo.
stabiler_kuehlmodusYesStabiler Kühlbetrieb gemäß Handbuch, keine reine Lüfterstufe und kein gerade wechselnder Zustand?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The read-only, closed-world annotations establish that this is a safe local operation, while the description adds the paired-reading and cooling-mode scope. It does not explain how measurement error is propagated, how an unstable cooling state is handled, or whether the result is only a difference or also an interpretation.

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 compact and front-loads the resource, measurements, and operating mode. The bilingual wording is somewhat redundant, and “einordnen” versus “Estimate” introduces slight uncertainty about whether classification or calculation is the primary result.

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 rich input schema and annotations provide enough information for basic invocation, and the description supplies a understandable selection context. With no output schema, however, the absence of result semantics, uncertainty handling, and unstable-mode behavior leaves meaningful gaps.

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%, including simultaneity, sensor placement, absolute error per measurement, and stable cooling operation, so the baseline is 3. “Paired AC readings” reinforces the temperature inputs but adds little beyond the schema and says nothing specific about fehler_je_c or stabiler_kuehlmodus.

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 clearly identifies the operation as assessing or estimating the temperature difference between intake and supply air from paired AC readings in cooling mode. It does not explicitly distinguish this paired-reading assessment from the sibling klima_abkuehltest_auswerten.

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?

“Im Kühlbetrieb” and “from paired AC readings” provide clear context for when the tool applies. However, the description itself omits the stable-cooling prerequisite stated in the schema and gives no when-not guidance or alternative tool.

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