Skip to main content
Glama

getecoback-climate-weather

entfeuchter_pruefpunkt_betriebsfenster

Read-only

Prüfe, welcher Teil der beobachteten Kellertemperatur im dokumentierten Betriebsfenster liegt — Check a cellar temperature span against the documented operating envelope

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": {
      "keller_min_c": "<keller_min_c>",
      "keller_max_c": "<keller_max_c>",
      "geraet_min_c": "<geraet_min_c>",
      "geraet_max_c": "<geraet_max_c>",
      "passender_pruefpunkt": "<passender_pruefpunkt>"
    },
    "name": "entfeuchter_pruefpunkt_betriebsfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraet_max_cYesObere Betriebsgrenze in °C laut Modellanleitung
geraet_min_cYesUntere Betriebsgrenze in °C laut Modellanleitung
keller_max_cYesHöchste beobachtete Kellertemperatur in °C
keller_min_cYesNiedrigste beobachtete Kellertemperatur in °C
passender_pruefpunktYesWasserentzug bei ähnlicher Temperatur und relativer Feuchte dokumentiert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 adds the semantic point that this is a span-against-envelope comparison (partial overlap, not a simple pass/fail), but says nothing about the result shape or about degenerate inputs such as min > max.

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 core German sentence is well front-loaded and compact. However, the English half restates the same content verbatim rather than adding information, which is duplicated wording an agent gains nothing from.

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 five-required-parameter tool with no output schema, the description should hint at what is returned — the phrase 'welcher Teil' implies a returned overlap interval, but the shape is never stated. The inputs are fully covered by the schema, so the gap is confined to the result side.

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 every parameter including the boolean 'passender_pruefpunkt' is already documented with units and bounds. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 3 applies.

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 uses a specific verb ('Prüfe') and names both operands precisely: the observed cellar temperature span versus the documented operating envelope ('Betriebsfenster'). It is clearly distinguishable from the sibling tools, which cover other distinct checks, though it never names an alternative itself.

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?

There is no guidance on when this check applies, what preconditions the inputs must satisfy, or how it relates to neighbouring checks such as the model-evidence or cold-comparison tools. The agent must infer the trigger condition entirely from the tool name and schema.

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