Skip to main content
Glama

getecoback-climate-weather

monoblock_kuehlrate_protokollierte_standortpaare

Read-only

Stellt zwei unterschiedlich lange Kühlbeobachtungen derselben Raumnutzung als °C pro Stunde gegenüber — Normalize observed air cooling across two differently timed placement trials.

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": {
      "abnahme_a_c": "<abnahme_a_c>",
      "abnahme_b_c": "<abnahme_b_c>",
      "dauer_a_min": "<dauer_a_min>",
      "dauer_b_min": "<dauer_b_min>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "monoblock_kuehlrate_protokollierte_standortpaare"
  }
}

Input Schema

NameRequiredDescriptionDefault
abnahme_a_cYesGemessener Temperaturabfall am gleichen Raumort im ersten Durchgang; negativ bei Anstieg.
abnahme_b_cYesGemessener Temperaturabfall im zweiten Durchgang.
dauer_a_minYesBeobachtungsdauer A in Minuten.
dauer_b_minYesBeobachtungsdauer B in Minuten.
vergleichbarYesVergleichbare Anfangslage, Sonne, Außenzustand und Einstellungen?

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 safe, closed-world nature is covered elsewhere. The description adds that the operation is a normalization into °C/h rather than a raw comparison, but it does not say what happens when "vergleichbar" is false (refusal, warning, or silent compute) nor what the result looks like. Useful but not rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operation is front-loaded, but the text is a bilingual pair where the English sentence is essentially a translation of the German one rather than an addition, so roughly half the wording is duplicative. Both halves are short, but neither adds information the other lacks.

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?

For a five-parameter pure-computation tool with full schema coverage, the description is close to sufficient: unit framing and the same-placement precondition are stated. The remaining gap is that, with no output schema, it never clarifies whether the result is two separate rates, a difference, or a single normalized figure.

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 all five parameters (including units, ranges and the meaning of negative abnahme) are already documented in the schema. The description contributes only the notion that the two durations differ and that the placement must be the same, which lightly frames "vergleichbar" but adds little beyond the schema.

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 ("stellt ... gegenüber" / "Normalize") on a specific resource (two air-cooling observations of differing durations) and states the output unit (°C per hour). It does not, however, distinguish this from neighbouring monoblock cooling tools such as monoblock_kuehlprobe_betrieb_nach_startphase, so an agent must rely on the name and schema to disambiguate.

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?

Usage is only implied: the phrase "unterschiedlich lange" plus "derselben Raumnutzung" signals the applicable situation (two trials of different duration on the same placement). There is no explicit when-not guidance, no mention of what to do if the trials are not comparable, and no named alternative tool for other cooling scenarios.

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