Skip to main content
Glama

getecoback-raumklima

gefriergeraet_abtau_ersatzlager

Read-only

Für ein freigegebenes Abtauen Zwischenlager und Unterbrechung abgleichen — Check cold-storage capacity and a documented interruption window before defrosting.

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": {
      "abtauen_erlaubt": "<abtauen_erlaubt>",
      "umzulagern_l": "<umzulagern_l>",
      "ersatz_frei_l": "<ersatz_frei_l>",
      "plan_min": "<plan_min>",
      "verfuegbar_min": "<verfuegbar_min>"
    },
    "name": "gefriergeraet_abtau_ersatzlager"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_minYesGeplante Unterbrechung einschließlich Wiederanlauf gemäß Anleitung.
umzulagern_lYesEigener geschätzter effektiver Platzbedarf der umzulagernden Waren in Litern.
ersatz_frei_lYesTatsächlich freier nutzbarer Platz im vorgesehenen geeigneten Ersatzgerät in Litern.
verfuegbar_minYesVerfügbarkeit des geeigneten Ersatzgeräts. Das ist keine Haltbarkeitsgrenze.
abtauen_erlaubtYesManuelles Abtauen ist für dieses Gerät in der Modellanleitung beschrieben?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 description correctly describes a non-mutating check. It adds useful framing that the interruption must be "gemäß Anleitung" (per the manual) and documented, but it never states the shape of the result (verdict, which constraint failed) despite having no output schema.

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 tight clauses, front-loaded with the precondition (approved defrost) before the task, with zero filler. The German/English duplication is slightly redundant but aids disambiguation of the domain terms rather than 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?

For a five-parameter, all-required, read-only validation tool with full schema coverage, the description covers the intent and precondition adequately. What is missing is the outcome contract — whether the call gates the defrost and how a failure is reported — which matters because there is no output schema to fall back on.

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%, with bounds (0–1440 min, 0–2000 L) and a clarifying note that verfuegbar_min is not a shelf-life limit, so the schema already carries the semantics. The description reinforces that both the storage capacity and the time window are inputs but adds no format or interpretation detail beyond that baseline.

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 action ("abgleichen" / "Check") and two concrete resources: intermediate cold storage capacity and a documented interruption window, scoped to defrosting a freezer. An agent can infer this is a feasibility/consistency check rather than a data fetcher. It stops short of explicitly saying it returns a pass/fail verdict, and it does not distinguish itself from freezer-related siblings such as gefriergeraet_eisschicht_verlauf.

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

Usage Guidelines3/5

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

Timing is implied ("before defrosting") and a precondition is stated ("für ein freigegebenes Abtauen" — only for an approved/authorized defrost). There is no explicit statement of when not to call it, no named alternative tool, and no mention of what to do if the reconciliation fails.

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