Skip to main content
Glama

getecoback-raumklima

gefrierschrank_24h_haushaltsspitze_und_bestandsvolumen

Read-only

Vergleiche zwei dokumentierte Gefrierschränke nach rollierender Frischmenge und belegtem Bestandsvolumen — Compare models by rolling 24-hour fresh load and retained volume

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": {
      "a_min": "<a_min>",
      "a_kg": "<a_kg>",
      "b_min": "<b_min>",
      "b_kg": "<b_kg>",
      "c_min": "<c_min>",
      "c_kg": "<c_kg>",
      "maximales_bestandsvolumen_l": "<maximales_bestandsvolumen_l>",
      "komplette_ladungsreihe": "<komplette_ladungsreihe>"
    },
    "name": "gefrierschrank_24h_haushaltsspitze_und_bestandsvolumen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kgYesFrisch zu gefrierende Masse der ersten Ladung
b_kgYesFrisch zu gefrierende Masse der zweiten Ladung
c_kgYesFrisch zu gefrierende Masse der dritten Ladung
a_minYesZeit der ersten beobachteten Frischladung seit Beginn der Erfassung
b_minYesZeit der nächsten Frischladung im selben Zeitmaßstab
c_minYesZeit der dritten Frischladung im selben Zeitmaßstab
komplette_ladungsreiheYesAlle relevanten Frischladungen und mindestens die vorangehenden 24 Stunden sind erfasst; keine zeitgleiche Doppelzählung
maximales_bestandsvolumen_lYesGrößter gleichzeitig geplanter Bestand einschließlich Neuware, als gemessenes beanspruchtes Volumen

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 and the bar is lower. The description adds nothing beyond the annotations: it does not say what a comparison result looks like, what happens when komplette_ladungsreihe is false, or how dual-counting is avoided. It also does not contradict the annotations, so this is a modest gap rather than an error.

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?

A single short sentence that leads with the verb and the comparison criteria, with only the bilingual restatement as near-redundant weight. Nothing is buried and there is no filler, though the second language half earns little beyond accessibility.

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?

Eight required parameters, a non-trivial domain computation (rolling 24-hour aggregation against retained volume), and no output schema mean the description carries a lot of burden. It does not explain the result, the meaning of the completeness flag, units of the time parameters beyond the schema, or any failure mode, leaving the agent under-informed for a tool of this complexity.

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 one of the eight required parameters already carries its own German description and range; the baseline of 3 applies. The description contributes no additional parameter meaning and does not resolve the mismatch between "zwei Gefrierschränke" and the single a/b/c load series.

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 verb ("Vergleiche") and resource ("zwei dokumentierte Gefrierschränke") and states the two comparison dimensions: rolling 24-hour fresh load and retained volume. It is distinguishable from the many sibling freezer tools, though it does not explain how the single set of a/b/c load parameters relates to "two" freezers, and it never names a sibling it is not.

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 to use this tool versus the numerous gefrierschrank_* siblings, and no prerequisites or exclusion conditions. The only hint is the topic itself; the agent must infer from the name alone whether this or e.g. gefrierschrank_schnelleinfrieren_protokoll_vorlauf is appropriate.

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