Skip to main content
Glama

getecoback-raumklima

lueften_messwirkung

Read-only

Vorher-nachher-Messung nach dem Lüften in Gramm pro Kubikmeter vergleichen — Measure whether room air actually held less water after ventilation.

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": {
      "before_c": "<before_c>",
      "before_rh_pct": "<before_rh_pct>",
      "after_c": "<after_c>",
      "after_rh_pct": "<after_rh_pct>",
      "same_position": "<same_position>"
    },
    "name": "lueften_messwirkung"
  }
}

Input Schema

NameRequiredDescriptionDefault
after_cYesLufttemperatur innen in °C.
before_cYesLufttemperatur innen in °C.
after_rh_pctYesRelative Feuchte der Raumluft in Prozent.
before_rh_pctYesRelative Feuchte der Raumluft in Prozent.
same_positionYesWaren Messort und Gerät vergleichbar und beide Messungen stabil?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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. The description adds the derived unit (g/m³) and the evaluative intent, but says nothing about how the result behaves when same_position is false, whether a warning or an invalid verdict is returned, or what shape the comparison takes.

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 clauses, front-loaded with the comparison first and the purpose second. The German and English halves restate each other, which is mild redundancy but keeps the definition scannable.

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?

Five required parameters with full schema coverage and no output schema, so the definition should explain the returned verdict and the effect of a negative same_position flag. It conveys the intent but leaves the outcome semantics unstated, which is a meaningful gap for a tool whose entire value is its verdict.

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 each of the five parameters is already documented in the schema, and the baseline is 3. The description only adds that the comparison is expressed in grams per cubic meter, which hints that temperature and relative humidity are combined into absolute humidity, but it does not explain that conversion or the role of same_position.

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?

Names a specific operation (before/after comparison of ventilation) and the quantity involved (grams per cubic meter), so an agent knows this evaluates the moisture actually removed by ventilating. It is distinct from dew-point siblings such as taupunkt_lueften, though it never explicitly contrasts itself with them.

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 phrase 'nach dem Lüften' and 'whether room air actually held less water' implies the use case (post-ventilation verification), but there is no explicit when-not guidance, no mention of prerequisites such as stable measurements, and no named alternative tool for related ventilation questions.

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