Skip to main content
Glama

getecoback-climate-weather

winterfenster_taupunkt_wechselintervall

Read-only

Zwischen zwei Oberflächenmessungen einen Wechsel der Taupunktseite eingrenzen — Bracket a change in surface dew-point margin without inventing an exact onset.

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": {
      "start_min": "<start_min>",
      "ende_min": "<ende_min>",
      "wand_start_c": "<wand_start_c>",
      "wand_ende_c": "<wand_ende_c>",
      "tau_start_c": "<tau_start_c>",
      "tau_ende_c": "<tau_ende_c>",
      "reserve_c": "<reserve_c>"
    },
    "name": "winterfenster_taupunkt_wechselintervall"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_minYesMinute des zweiten Messpaars auf derselben Achse.
reserve_cYesEigene Messreserve in °C. Innerhalb dieser Zone keine eindeutige Seite ausweisen.
start_minYesMinute des ersten Messpaars auf gemeinsamer Achse.
tau_ende_cYesRaumtaupunkt zum zweiten Messzeitpunkt.
tau_start_cYesRaumtaupunkt zum ersten Messzeitpunkt.
wand_ende_cYesDieselbe Oberfläche am Ende.
wand_start_cYesOberfläche zu Beginn.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly and closed-world, so the safety profile is covered. The description adds real behavioral content: the result is a bracket/interval rather than an exact onset, and reserve_c creates a zone where no clear side is reported — context the agent would not get from the schema alone. It still does not state units of the returned interval or how ties are handled beyond the reserve.

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?

One compact sentence with the key constraint ('bracket, not exact onset') front-loaded. The bilingual restatement is a small redundancy but arguably useful for a German-named tool, and nothing else is wasted.

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 7-required-parameter, annotation-covered pure computation with no output schema, the definition should explain what the returned bracket looks like and what 'Seite' means. Those gaps are noticeable, though the input side is fully covered by the schema.

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 every parameter is already documented in German with ranges. The description adds only the conceptual framing that the two measurement pairs must share one axis; it contributes no meaning beyond what the schema carries, making the baseline 3 appropriate.

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?

States a specific verb (eingrenzen/bracket) and object (Wechsel der Taupunktseite zwischen zwei Oberflächenmessungen), which is distinguishable from siblings such as winterfenster_oberflaeche_erholt_sich_spaeter. The domain term 'Taupunktseite' is never explained, so an agent unfamiliar with the concept must infer it from the parameter names.

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 framing 'between two surface measurements' and 'without inventing an exact onset' implies the situation this tool fits — when only two samples exist and the transition cannot be pinned precisely. No explicit when-not or named alternative is given, so selection relies on inference.

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