Skip to main content
Glama

getecoback-raumklima

taupunkt_lueften

Außentaupunkt mit geschätzter Wandtemperatur vergleichen. — Compare outdoor dew point (Magnus approximation) with a wall estimate 2 °C below room temperature. A drying decision also needs indoor humidity and a measured coldest surface.

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_temp_c": "<aussen_temp_c>",
      "aussen_luftfeuchte_prozent": "<aussen_luftfeuchte_prozent>",
      "innen_temp_c": "<innen_temp_c>"
    },
    "name": "taupunkt_lueften"
  }
}

Input Schema

NameRequiredDescriptionDefault
innen_temp_cYesInnen-/Kellertemperatur in °C (Wände werden 2 °C kühler gerechnet)
aussen_temp_cYesAußentemperatur in °C
aussen_luftfeuchte_prozentYesRelative Luftfeuchte außen in % (5–100)

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?

No annotations exist, so the description carries the full burden. It does disclose the computational approach (Magnus approximation) and the modelling assumption (walls 2 °C cooler than room temperature), which is real behavioral context. It does not say what the comparison yields — a boolean verdict, a margin in °C, or a recommendation — leaving the outcome opaque for a decision tool.

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 tight sentences, with the core comparison stated first and the caveat second. The German-then-English duplication adds length but serves bilingual disambiguation and each version carries the same substantive content, so it is only mildly redundant.

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 three-parameter computation with no annotations and no output schema, the description covers the method and the key assumption, which is most of what is needed. The missing piece is the return value: without an output schema the description should say what the comparison produces, and it does not.

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 including the 5–100 % humidity range and the 2 °C wall offset. The description restates the wall-offset assumption rather than adding new meaning such as acceptable ranges, unit edge cases, or how the inputs are combined. Baseline 3 applies.

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 operation: comparing outdoor dew point (via Magnus approximation) against a wall temperature estimated 2 °C below room temperature. That is a clear verb+resource statement an agent can act on. It stops short of naming any sibling tool by name, so the boundary with the other 'lueften' tools is only implicit.

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 closing sentence signals a usage limit — a drying decision also needs indoor humidity and a measured coldest surface — which usefully implies this tool alone is not sufficient. However, it never states when to prefer this over the sibling tools or what precondition must hold before calling it; usage is implied rather than prescribed.

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