Skip to main content
Glama

getecoback-climate-weather

gefrierfach_ladungsversuch_gleichzeitige_ereignisse

Read-only

Trenne eine zusammenhängend belegte Ladungsphase von zusätzlicher Tür- und Wärmelast — Check whether a fresh-load energy observation remained isolated

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": {
      "ladung_beginnt_min": "<ladung_beginnt_min>",
      "nachprobe_ende_min": "<nachprobe_ende_min>",
      "weitere_tuer_erste_min": "<weitere_tuer_erste_min>",
      "raumereignis_min": "<raumereignis_min>",
      "lueckenlose_beobachtung": "<lueckenlose_beobachtung>"
    },
    "name": "gefrierfach_ladungsversuch_gleichzeitige_ereignisse"
  }
}

Input Schema

NameRequiredDescriptionDefault
raumereignis_minYesErste getrennte Änderung der Wärmebelastung, 0 ohne beobachtete Änderung
ladung_beginnt_minYesBeginn des beobachteten Beladens
nachprobe_ende_minYesEnde des vorab geplanten Nachbeobachtungsfensters
weitere_tuer_erste_minYesErste weitere Türöffnung nach Beginn; 0 wenn keine erfasst
lueckenlose_beobachtungYesTür- und Aufstellraumprotokoll liegen für das gesamte Fenster vor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description adds nothing: it does not say what the computed result means (boolean separation? intervals?), how missing door/heat events are treated, or what happens when observation is not gap-free — a material behavior given the 'lueckenlose_beobachtung' flag.

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, but the two-language restatement ('Trenne ... — Check whether ...') is not a clean parallel and reads as duplicated rather than reinforcing content, leaving the reader unsure whether these are the same task or two phases.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter computation with no output schema, yet the description never indicates the shape or meaning of the result or how the gap-free flag changes the answer. For a tool with no structured return documentation, that is a significant omission.

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% and every parameter carries its own German description with ranges and zero-sentinels, so the schema does the heavy lifting. The prose only echoes the concepts (Tür-/Wärmelast) without adding format or edge-case detail, matching the baseline 3.

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 gives a verb and a concept ('Trenne eine zusammenhängend belegte Ladungsphase von zusätzlicher Tür- und Wärmelast', glossed as checking whether a fresh-load observation stayed isolated), so the general intent is inferable. However, the two clauses are not clearly the same operation, and nothing distinguishes it from the many other event-separation tools in the sibling list.

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 to use this tool, when not to, or which alternative (e.g. the other gefrierfach/ereignis tools) to pick instead. The agent must guess from the 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