Skip to main content
Glama

getecoback-raumklima

heizpause_oberflaeche_luft_trend_gegenlaeufig

Read-only

Unterscheide einen gleichläufigen und einen gegenläufigen Trend von Wand und Luft nach einem Heizwechsel — Detect diverging wall and air trends after heating changes

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": {
      "wand_a_c": "<wand_a_c>",
      "wand_b_c": "<wand_b_c>",
      "luft_a_c": "<luft_a_c>",
      "luft_b_c": "<luft_b_c>",
      "aenderungstoleranz_c": "<aenderungstoleranz_c>",
      "messorte_unveraendert": "<messorte_unveraendert>"
    },
    "name": "heizpause_oberflaeche_luft_trend_gegenlaeufig"
  }
}

Input Schema

NameRequiredDescriptionDefault
luft_a_cYesErste gleichzeitige Innenluftablesung
luft_b_cYesZweite gleichzeitige Innenluftablesung
wand_a_cYesWandmesswert bei erster Ablesung
wand_b_cYesWandmesswert beim gleichen Messpunkt später
aenderungstoleranz_cYesEigene kombinierte Toleranz für die Veränderung je Messreihe
messorte_unveraendertYesMessorte und Messarten sind unverändert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 conceptual operation (comparing wall and air trends in the same direction vs. opposing), but says nothing about what is returned (a classification label?), how the tolerance interacts with the comparison, or what happens when measurements are deemed invalid.

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?

One front-loaded sentence with the core action first; the German and English halves are redundant but the English version aids cross-language routing. No filler or tangents.

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?

Six required numeric/boolean parameters, no output schema, and the description never states the result the tool produces (e.g., a 'gleichläufig' vs. 'gegenläufig' verdict) or the tolerance semantics. For a classification tool with no annotated output contract, this leaves the agent guessing about the return value.

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 every parameter (the two wall readings, two air readings, tolerance, and the unchanged-measurement-locations flag) is already documented in the schema. The description adds no further meaning such as measurement ordering, simultaneous-reading requirements, or how the tolerance is applied.

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?

A specific verb ('Unterscheide') plus the two compared quantities (Wand vs. Luft) and the operation (Trend nach einem Heizwechsel) make the intent readable. It does not distinguish itself from siblings such as heizpause_durchlaufen_wiederaufheizen or heizpause_raumfolge_wiederanlauf_engpass, so an agent must infer the boundary from the name 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?

The only situational cue is 'nach einem Heizwechsel', which merely restates the 'heizpause'/'Heizwechsel' framing already present in the tool name. There is no guidance on when to pick this over related heating-pause tools, no prerequisites, and no exclusions.

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