Skip to main content
Glama

getecoback-climate-weather

luftfeuchte_bei_temperaturwechsel

Read-only

Relative Feuchte nach Heizen oder Abkühlen ohne Feuchtenachschub abschätzen — Estimate changed relative humidity for a fixed air-water mass.

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": {
      "initial_c": "<initial_c>",
      "initial_rh_pct": "<initial_rh_pct>",
      "final_c": "<final_c>"
    },
    "name": "luftfeuchte_bei_temperaturwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
final_cYesLufttemperatur innen in °C.
initial_cYesLufttemperatur innen in °C.
initial_rh_pctYesRelative Feuchte der Raumluft in Prozent.

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 a genuine behavioural assumption — constant air-water mass with no moisture added — which is the key modelling constraint. It does not state that the result is an approximation from a physical formula or whether it accounts for condensation when dew point is crossed, which matters for a cooling case.

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 purpose stated before the English gloss; nothing redundant. The bilingual restatement is slightly duplicative but serves a real clarity function for a German-named tool.

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 simple three-parameter calculation with no output schema, the definition covers the model assumption but omits what is actually returned (presumably percent RH) and any edge-case note such as condensation during cooling. Adequate but leaves gaps an agent would need to guess at.

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% and all three parameters carry descriptions, so the baseline is 3. However, initial_c and final_c both have the identical schema text 'Lufttemperatur innen in °C.', and the description does not disambiguate which one is the before vs. after temperature — the one place where added meaning would have helped.

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?

Uses a specific verb ('abschätzen'/'Estimate') with a specific resource ('changed relative humidity'), and the qualifier 'nach Heizen oder Abkühlen ohne Feuchtenachschub' scopes the operation to a fixed air-water mass. An agent can tell this is a humidity-after-temperature-change calculation, though no sibling is named to sharpen the boundary.

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 Heizen oder Abkühlen ohne Feuchtenachschub' implies the applicable situation (a sealed air mass whose temperature changes), but there is no explicit when-to-use statement, no prerequisite about which temperature is treated as initial vs. final, and no routing to any alternative tool.

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