Skip to main content
Glama

getecoback-climate-weather

keller_aussen_hygrometer_zielwert_oberflaechenreserve

Read-only

Zu einer Außenlufttemperatur den rechnerischen Feuchte-Zielwert für die gemessene Kellerwand ableiten — Calculate the outdoor relative-humidity marker corresponding to a dew-point margin.

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": {
      "aussen_c": "<aussen_c>",
      "wand_c": "<wand_c>",
      "reserve_c": "<reserve_c>"
    },
    "name": "keller_aussen_hygrometer_zielwert_oberflaechenreserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
wand_cYesKälteste dokumentierte Kelleroberfläche.
aussen_cYesZeitgleich vor Ort gemessene Außentemperatur.
reserve_cYesEigener Puffer zwischen Ziel-Taupunkt und Oberfläche in °C.

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 the safety profile is covered. The description adds that the value is 'rechnerisch' and rests on a dew-point margin, which is useful behavioral context. It does not say whether the result is a percentage, a temperature, or how the margin is applied — a real gap given there is no output schema.

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 plus an English restatement, with no padding. The bilingual duplication is slightly redundant but each half adds a nuance rather than repeating verbatim.

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?

With no output schema, the description carries the burden of describing the returned value, and it remains ambiguous whether the result is a relative humidity in percent or a dew-point temperature. For a pure three-input calculation this leaves a meaningful hole for correct interpretation of the result.

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 the schema already documents all three parameters in detail. The description only adds the conceptual linkage (outdoor temperature + measured wall + dew-point margin) and does not explain units or how reserve_c enters the calculation beyond what the schema's 'Puffer zwischen Ziel-Taupunkt und Oberfläche' already says.

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 computation (deriving a humidity target value) and the concrete inputs it is derived from (outdoor air temperature, measured basement wall). The German and English halves diverge slightly — one says 'Feuchte-Zielwert für die gemessene Kellerwand', the other 'outdoor relative-humidity marker' — so an agent can identify the tool's job but not the exact output quantity.

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 description implies the calculation context (deterministic derivation from three measured temperatures) but never states when to prefer this over the many sibling hygrometer tools, nor any preconditions or exclusions. Usage must be inferred from the parameter 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