Skip to main content
Glama

getecoback-raumklima

sommerlueftung_stossfolgen_zwischenwaerme

Read-only

Trennt zwei gemessene Abkühlungen während des Lüftens von der Wiedererwärmung zwischen den beiden Stoßphasen — Separate two observed cooling intervals from warming between them.

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": {
      "vor_erster_phase_c": "<vor_erster_phase_c>",
      "nach_erster_phase_c": "<nach_erster_phase_c>",
      "vor_zweiter_phase_c": "<vor_zweiter_phase_c>",
      "nach_zweiter_phase_c": "<nach_zweiter_phase_c>"
    },
    "name": "sommerlueftung_stossfolgen_zwischenwaerme"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_erster_phase_cYesRaumwert vor erster Öffnung in °C.
nach_erster_phase_cYesWert nach erstem Fensterschluss in °C.
vor_zweiter_phase_cYesWert vor zweiter Öffnung in °C.
nach_zweiter_phase_cYesWert nach zweitem Fensterschluss in °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, but the description adds no behavioral context beyond the conceptual split — not what result is produced, in what units, or how the two cooling deltas versus the intermediate warming are expressed. For a pure computation with no output schema, that absence is a real gap.

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?

A single front-loaded sentence with the core semantics stated first. The German/English duplication is redundant but intentional and does not bury the meaning.

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?

Four required, well-documented parameters and a read-only profile make the call itself unambiguous, but with no output schema the agent is left not knowing what the return value looks like or how the separated quantities are reported. The description should have closed that gap.

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%, with each of the four required parameters labeled as a room value before/after the first and second window openings in °C. The description confirms the phase pairing conceptually but adds no format, ordering, or validation meaning beyond the schema.

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 gives a specific verb ("Trennt"/"Separate") and names both resources: the two measured cooling intervals and the rewarming between the two burst-ventilation phases. It is clear what computation is performed, though it never distinguishes itself from the related sibling sommerlueftung_tiefpunkte_zur_offenphase.

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?

No when-to-use or when-not-to-use guidance is given, nor any prerequisite about when the measurement series is complete enough to separate cooling from rewarming. The agent must infer the usage context from the name and the parameter labels alone.

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