Skip to main content
Glama

getecoback-climate-weather

gefrierschrank_schnelleinfrieren_protokoll_vorlauf

Read-only

Prüfe, ob eine dokumentierte Schnelleinfrierphase rechtzeitig zum beobachteten Beladen begann — Verify the observed lead time for the manual-documented fast-freeze mode

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>",
      "modus_ab_min": "<modus_ab_min>",
      "ladung_ab_min": "<ladung_ab_min>",
      "vorlauf_soll_min": "<vorlauf_soll_min>",
      "modus_und_ladungsscope_bestaetigt": "<modus_und_ladungsscope_bestaetigt>"
    },
    "name": "gefrierschrank_schnelleinfrieren_protokoll_vorlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
modus_ab_minYesProtokollierter Beginn der bestätigten Funktion auf gemeinsamer Zeitbasis
ladung_ab_minYesZeitpunkt des Beladens auf gleicher Zeitbasis
genaues_modellYesGenaue deutsche Modellkennung laut Typenschild
vorlauf_soll_minYesZum Ladungsfall dokumentierter Vorlauf aus passender Geräteanleitung
modus_und_ladungsscope_bestaetigtYesAnleitung bestätigt den Vorgang und die beobachtete Aktivierung für diesen Fall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a verification of a manual-documented fast-freeze lead time and depends on confirmation of scope, but it does not describe outcome behavior or what happens when the scope is unconfirmed.

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?

The description is short and front-loads the core check with 'Prüfe, ob ...'. The German and English rendering are redundant, but the sentence remains clear and contains no extraneous explanation.

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-parameter verification tool with fully described schema fields and read-only annotations, the description is adequate. However, it does not state the expected result shape or behavior when confirmation fields are false, which leaves some operational ambiguity.

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 are already documented in the input schema. The description adds only the conceptual relationship between documented fast-freeze start, observed loading time, and target lead time; it does not add syntax, constraints, or unit details 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 gives a specific verb ('Prüfe' / 'Verify') and a precise resource: whether a documented fast-freeze phase started early enough relative to observed loading, including the manual-documented lead time. It is clearly distinct in topic from most freezer-related siblings, but it does not explicitly differentiate itself from any named alternative.

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?

The description states what is checked but gives no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives. Usage is only implied by the phrase 'dokumentierte Schnelleinfrierphase' and the verification framing.

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