Skip to main content
Glama

getecoback-raumklima

punktwaerme_raumdurchschnitt_verdeckt_festen_platz

Read-only

Eine Verbesserung im Raumaggregat gegen die direkt am festen Nutzplatz gemessene Änderung prüfen — Check whether a rising room index masked deterioration at the occupied point.

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": {
      "raum_frueh_c": "<raum_frueh_c>",
      "raum_spaet_c": "<raum_spaet_c>",
      "platz_frueh_c": "<platz_frueh_c>",
      "platz_spaet_c": "<platz_spaet_c>",
      "mindest_aenderung_c": "<mindest_aenderung_c>",
      "vergleichbare_messgroesse": "<vergleichbare_messgroesse>"
    },
    "name": "punktwaerme_raumdurchschnitt_verdeckt_festen_platz"
  }
}

Input Schema

NameRequiredDescriptionDefault
raum_frueh_cYesMittel derselben räumlichen Referenzpunkte vor dem Versuch, ohne Nutzplatz.
raum_spaet_cYesSpäteres Mittel derselben Referenzpunkte.
platz_frueh_cYesWert am festen Arbeitspunkt vor dem Versuch.
platz_spaet_cYesSpäterer Wert am selben Arbeitspunkt.
mindest_aenderung_cYesKleinste auswertbare Änderung bei beiden Größen in °C.
vergleichbare_messgroesseYesVorher/nachher und Raumpunkte/Nutzplatz mit kompatibler Messgröße, gleichzeitigen Beobachtungen und stabiler Geometrie?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered and the description need only add analytical context. It does convey the masking-test intent, but says nothing about how mindest_aenderung_c gates the verdict, what conclusion is produced when room rises while the point falls, or what the response contains. Adequate but shallow for a verdict-producing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence pair, with the German statement followed by the English gloss so both audiences get the intent immediately. The core idea (room aggregate vs. occupied point) is front-loaded and nothing is wasted.

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?

Six required numeric/boolean parameters with full schema documentation and an annotation-covered safety profile mean the agent can call it, and no output schema needs explaining. What is missing is the interpretive layer — what a positive versus negative finding means and how the minimum-change threshold affects the verdict — which matters for a diagnostic decision 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 six parameters carry their own German descriptions, so the schema does the heavy lifting. The description adds no extra meaning about the two pairing assumptions (raum_frueh/spaet vs. platz_frueh/spaet) or how vergleichbare_messgroesse interacts with the check, which is the baseline 3 case.

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 specific diagnostic operation: comparing a room-aggregate improvement against the change measured directly at the fixed occupied point, i.e. detecting a masked deterioration. That is a clear verb-plus-comparison, not a restatement of the name. It does not, however, distinguish itself from near-neighbours such as punktwaerme_verdeckter_unterschied_koerperzonen or punktwaerme_routenvergleich_einzelplatz_dominiert.

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

Usage Guidelines3/5

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

The phrasing 'prüfen — check whether a rising room index masked deterioration' implies the scenario that selects this tool (room average improving while the occupied point may be getting worse). There is no explicit when-not guidance and no named alternative tool for the competing analyses, so selection still requires inference from sibling names.

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