Skip to main content
Glama

getecoback-raumklima

winterluft_feuchte_rueckkehr_wiedererwaermt

Read-only

Nach dem Wiederaufwärmen den Rücklauf des Dampfdrucks ins Vorlüftungsniveau einordnen — Quantify moisture rebound using three dew-point observations.

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": {
      "vorher_tau_c": "<vorher_tau_c>",
      "frueh_tau_c": "<frueh_tau_c>",
      "warm_tau_c": "<warm_tau_c>",
      "zusammenpassend": "<zusammenpassend>"
    },
    "name": "winterluft_feuchte_rueckkehr_wiedererwaermt"
  }
}

Input Schema

NameRequiredDescriptionDefault
warm_tau_cYesRaumtaupunkt beim wieder erwärmten Raum.
frueh_tau_cYesRaumtaupunkt nach dem Öffnen, sobald die Anzeige stabil ist.
vorher_tau_cYesRaumtaupunkt vor dem Luftaustausch.
zusammenpassendYesEin Raum, gleiche Sensorposition und alle drei Werte überwiegend repräsentativ?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 safety is covered and the bar is lower. The description adds the useful behavioral frame that the result is a comparison against the pre-ventilation level, but says nothing about what the classification looks like or how the comparison is reported.

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

Conciseness3/5

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

The definition is short, but the two clauses are a German/English restatement of the same idea rather than complementary information, and the German half is dense idiom that costs the reader effort without adding precision. The concrete part should have led.

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?

For a four-parameter read-only computation with no output schema, the description never states what the tool returns — a label, a delta, a pass/fail — leaving the agent unable to interpret the response. The annotations cover the safety profile, so this is the main remaining 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 coverage is 100%, so all four parameters (including the zusammenpassend plausibility boolean) are already documented in the schema. The description's "three dew-point observations" merely echoes the schema and adds no meaning about value ranges, units, or the consequence of zusammenpassend=false. Baseline 3 applies when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The English clause names a concrete action ("Quantify moisture rebound using three dew-point observations"), but the German lead sentence is metaphorical jargon ("Rücklauf des Dampfdrucks ins Vorlüftungsniveau einordnen") that obscures the actual operation. It also gives no hint of how it differs from near-neighbours such as entfeuchtung_rueckkehr_nach_pause or bad_feuchte_erholung_protokoll.

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?

"Nach dem Wiederaufwärmen" supplies an implicit temporal precondition, which is more than nothing. However, there is no explicit when-not guidance, no mention of which sibling to choose for the pre-ventilation or drying-pause case, and no stated prerequisite that the three readings come from a single sensor position.

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