Skip to main content
Glama

getecoback-climate-weather

gefrierschrank_aufstellort_klimaband_messabdeckung

Read-only

Beurteile die dokumentierte Zeit unter und über dem Modell-Klimaband inklusive offener Zeit — Scope logged ambient conditions to the exact freezer climate 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": {
      "genaues_modell": "<genaues_modell>",
      "dauer_min": "<dauer_min>",
      "luecke_min": "<luecke_min>",
      "unter_10_min": "<unter_10_min>",
      "ueber_43_min": "<ueber_43_min>",
      "messpunkte_passend": "<messpunkte_passend>"
    },
    "name": "gefrierschrank_aufstellort_klimaband_messabdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_minYesGesamtdauer der geplanten Aufstellortbeobachtung
luecke_minYesMinuten ohne verwertbare Messwerte
ueber_43_minYesBelegte Minuten über 43 °C am selben Messort
unter_10_minYesBelegte Minuten unter 10 °C am vorgesehenen Gerätelufteintritt
genaues_modellYesGenaue deutsche Modellkennung
messpunkte_passendYesZeitanteile sind getrennt und repräsentieren den Aufstellort, keine Wetter-App oder Innenfachtemperatur

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 and the bar is lower. The description adds one genuinely useful behavioral point — that open/gap time is included in the assessment ('inklusive offener Zeit') — but says nothing about what the verdict or output of the assessment looks like, which matters since no output schema exists.

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?

It is short and front-loaded with the main action, which is good. But the second half is a loose English restatement of the German rather than new information, so half the text is redundant padding.

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?

All six required parameters are described in the schema, so input-side completeness is fine. For a judgment/computation tool with no output schema, though, the description never explains what result is produced (a pass/fail verdict, a breakdown of minutes, a warning), which leaves a real gap for invocation and interpretation.

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 (dauer_min, luecke_min, unter_10_min, ueber_43_min, genaues_modell, messpunkte_passend) is already documented in the schema and the baseline is 3. The description's mention of 'offener Zeit' loosely maps to luecke_min but adds no format, unit, or validation meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Beurteile') and a resource ('die dokumentierte Zeit unter und über dem Modell-Klimaband inklusive offener Zeit'), so the general purpose — assessing logged durations against a model-specific climate band — comes across. However, the English tail only restates the German in vaguer terms ('Scope logged ambient conditions to the exact freezer climate envelope') and gives no differentiation from the many closely named gefrierschrank_* siblings that also deal with climate/measurement evidence.

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 statement of when this tool should be chosen, no prerequisites (e.g. that measurements must already be logged), and no exclusion or alternative named among the numerous sibling freezer tools. The agent must infer the usage context from the tool name alone.

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