Skip to main content
Glama

getecoback-raumklima

fenster_kuehlpause_nach_passiver_probe

Read-only

Ermittelt aus zwei vorhandenen Messpunkten, ob das eigene Temperaturziel nach passiver Kühlung noch erfüllt war — Check whether two post-cooling readings still meet a user target before considering active cooling.

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": {
      "frueher_c": "<frueher_c>",
      "spaeter_c": "<spaeter_c>",
      "ziel_c": "<ziel_c>",
      "gleiche_messstelle": "<gleiche_messstelle>"
    },
    "name": "fenster_kuehlpause_nach_passiver_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_cYesEigener Vergleichszielwert für diesen Platz in °C.
frueher_cYesErste nach passiver Kühlung am Nutzungsplatz beobachtete Temperatur in °C.
spaeter_cYesSpätere Ablesung beim nächsten Nutzungsbeginn in °C.
gleiche_messstelleYesGleicher Ort und vergleichbare Messung für beide Ablesungen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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. The description usefully adds that the calculation is purely retrospective ('aus zwei vorhandenen Messpunkten', 'post-cooling readings'), but with no output schema it says nothing about the form of the result or how a borderline outcome is treated.

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 compact sentences, front-loaded with the computation and followed by the purpose, with the German/English mirror aiding comprehension of an unusual domain term. The bilingual duplication is slightly redundant but not wasteful at this length.

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 four-parameter decision tool with no output schema, the definition leaves a real gap: it never states what the caller receives (a verdict, a boolean, a recommendation) nor how the two readings are combined against the target. The purpose and usage context are otherwise adequate.

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 the meaning of ziel_c, frueher_c, spaeter_c and gleiche_messstelle is already documented, including ranges and units. The description only restates that the readings are post-cooling and that the target is user-defined, adding marginal value 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 ('Ermittelt aus zwei vorhandenen Messpunkten') on a specific subject ('ob das eigene Temperaturziel nach passiver Kühlung noch erfüllt war'), so an agent knows it is an evaluation of two existing readings against a user-defined target rather than a new measurement. It is not explicitly contrasted with a named sibling, which keeps it below a 5.

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

Usage Guidelines4/5

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

The clause 'before considering active cooling' gives a clear decision-gate context: call this to decide whether active cooling is still needed. No exclusions or prerequisites (e.g. what to do if readings were at different locations) are stated, so it stops short of full when/when-not guidance.

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