Skip to main content
Glama

getecoback-raumklima

luftkuehler_kuehlakku_zusatzsignal_auslass_sitz

Read-only

Prüft ob ein gegenüber Wasserbetrieb gemessener Akkueffekt am Auslass auch am Sitz erscheint — Check whether extra cooling at the outlet also reaches the chosen seat.

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": {
      "auslass_zusatz_c": "<auslass_zusatz_c>",
      "sitz_zusatz_c": "<sitz_zusatz_c>",
      "toleranz_c": "<toleranz_c>",
      "gleiche_phase": "<gleiche_phase>"
    },
    "name": "luftkuehler_kuehlakku_zusatzsignal_auslass_sitz"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranz_cYesUnterscheidungsbreite der Messreihe in °C.
gleiche_phaseYesZeitgleiche Werte aus derselben dokumentierten Akkuphase, jeweils relativ zur passenden Wasserprobe?
sitz_zusatz_cYesGemessener Zusatzabfall am Sitzplatz in °C.
auslass_zusatz_cYesGemessener zusätzlicher Temperaturabfall am Auslass in °C.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful behavioral hint that this is a pure comparative evaluation of supplied values rather than a new measurement, but it says nothing about the verdict criteria, tolerance handling, or what the result looks like.

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?

Two short bilingual sentences with the core condition front-loaded and no filler. The German/English duplication is deliberate and not wasteful, though the sentence structure ('am Auslass auch am Sitz erscheint') is slightly compressed.

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?

All four required parameters are documented in the schema and the safety profile comes from annotations, so the definition is callable. But with no output schema, the description should state what the check returns (a verdict? a boolean? a comparison against toleranz_c) and it does not, leaving a real gap for an evaluation 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%, so all four parameters (toleranz_c, gleiche_phase, sitz_zusatz_c, auslass_zusatz_c) are already documented in the schema. The description only echoes the outlet/seat pairing and adds no semantics for the tolerance width or the same-phase flag. Baseline 3 applies when the schema does the heavy lifting.

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 concrete operation — a check of whether the cooling-pack effect measured at the outlet (relative to water operation) also appears at the seat — with specific verb and subject rather than restating the name. It does not, however, contrast itself against any of the many sibling luftkuehler_kuehlakku_* checks, so an agent must infer the distinction from the wording alone.

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 explicit when-to-use statement, no preconditions (e.g. that a water-operation baseline must already be measured), and no named alternative such as luftkuehler_kuehlakku_vor_nach_gegen_wasserprobe. The agent can only infer applicability from the phrase 'gegenüber Wasserbetrieb gemessener Akkueffekt'.

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