Skip to main content
Glama

getecoback-climate-weather

schlafzimmer_hitzestunden_messreihe

Read-only

Dauer über einem selbst gesetzten Temperaturziel aus vier Nachtmessungen abschätzen — Estimate hot hours and degree-hours from four equally spaced readings.

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_c": "<start_c>",
      "danach_c": "<danach_c>",
      "spaeter_c": "<spaeter_c>",
      "ende_c": "<ende_c>",
      "intervall_min": "<intervall_min>",
      "ziel_c": "<ziel_c>"
    },
    "name": "schlafzimmer_hitzestunden_messreihe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_cYesVierter Messwert in °C.
ziel_cYesEigener Vergleichswert in °C, kein Gesundheits- oder Sicherheitswert.
start_cYesErster Messwert in °C.
danach_cYesZweiter Messwert in °C.
spaeter_cYesDritter Messwert in °C.
intervall_minYesGleich großer Zeitabstand in Minuten zwischen allen aufeinanderfolgenden Messungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 by structured data. The description adds one genuinely useful behavior signal — that the result is an estimate ('abschätzen') rather than an exact measurement, and that the target is user-chosen, not a health threshold — but says nothing about precision, assumptions of linear interpolation, or edge cases when readings sit below the target.

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 sentences with the core purpose front-loaded. The German and English halves are near-duplicates, which is defensible for a bilingual catalog but means part of the text is restatement rather than added information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly names both outputs (hot hours and degree-hours), and the fully-covered input schema plus read-only annotations carry the rest. Only the estimation method's assumptions are left unstated, which is a modest gap for a pure-function calculator.

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 all six parameters, their ranges, and their meaning are already documented. The description echoes two of them ('four equally spaced readings', 'self-set temperature target') but adds no new semantics, such as whether readings must be in chronological order or what happens if the series crosses the target multiple times.

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 concrete verb ('abschätzen' / 'Estimate') and a concrete resource ('hot hours and degree-hours') from a clearly bounded input ('four equally spaced readings'). An agent can tell this is a thermal-exposure estimation tool, but the description never names or contrasts a sibling such as messreihe_echte_wiederholungen_zaehlen, so differentiation is left to inference.

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 'aus vier Nachtmessungen' and 'selbst gesetzten Temperaturziel' implies the situation (a night-time temperature series compared against a user-chosen target), which is enough to recognize when the tool fits. However, there is no explicit when-not guidance and no alternative tool is named for related measurement-series 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