Skip to main content
Glama

getecoback-climate-weather

klimafenster_kuehlprobe_zwei_nutzungsorte

Read-only

Prüft bei einer Raumprobe die Abweichung von zwei selbst gewählten Temperaturzielen an zwei konkreten Nutzungsplätzen — Check a single run against two user-chosen temperature targets at separate locations.

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": {
      "sitz_c": "<sitz_c>",
      "zweiter_ort_c": "<zweiter_ort_c>",
      "ziel_sitz_c": "<ziel_sitz_c>",
      "ziel_zweiter_c": "<ziel_zweiter_c>",
      "ortswerte_vergleichbar": "<ortswerte_vergleichbar>"
    },
    "name": "klimafenster_kuehlprobe_zwei_nutzungsorte"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitz_cYesMesswert am regelmäßig genutzten Sitzplatz in °C.
ziel_sitz_cYesEigener Vergleichszielwert am Sitzplatz in °C.
zweiter_ort_cYesZeitgleicher Messwert am zweiten Nutzungsort in °C.
ziel_zweiter_cYesEigener Vergleichszielwert am zweiten Ort in °C.
ortswerte_vergleichbarYesSensoren und Abschattung geprüft, zur selben Zeit beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 agent knows this is a safe, self-contained computation. The description adds the meaningful scope constraint that it evaluates a single run rather than an aggregate, but says nothing about what happens when the values are not comparable or what kind of result is produced. With safety covered by annotations, this is adequate but thin.

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, front-loaded with the verb and the core constraint, with the English mirror sentence aiding disambiguation. The bilingual duplication is slightly redundant but justified for a German-named tool with an opaque name.

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 five required parameters, no output schema and only minimal annotations, the definition should say something about the shape of the result (per-location deviations? a pass/fail?) and about the effect of the comparability flag. Those gaps leave the agent able to call it but unsure how to interpret or report the outcome.

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 five parameters carry their own German descriptions including units (°C) and ranges, so the schema does the heavy lifting. The description only restates the two-location, two-target framing already visible in the schema; it adds no interpretation of how 'ortswerte_vergleichbar' gates the check. Baseline 3 is 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?

The description names a concrete verb ('Prüft ... die Abweichung') and a concrete resource (deviation between two measured values and two user-chosen targets at two named usage spots), so an agent knows exactly what is computed. It does not, however, contrast itself with any sibling tool, so the agent must infer from names alone which variant applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes the scenario ('bei einer Raumprobe', i.e. a single measurement run) but never states when to prefer this over the many other two-location or two-target checks in the sibling list, nor any exclusion such as not using it for time-series or multi-day comparisons. No prerequisites or alternatives are given.

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