Skip to main content
Glama

getecoback-climate-weather

kuehlschrank_kaltes_fach_grosse_schale_ablagebelegung

Read-only

Prüft die praktisch nutzbare Kühlablage für eine große Schale zusammen mit belegter zweiter Ablage, wenn der restliche Kühlschrankinhalt bleiben soll — Check simultaneous tray and shelf use in one witnessed refrigerator layout

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": {
      "gleiche_ablagenstellung": "<gleiche_ablagenstellung>",
      "schale_einschieben": "<schale_einschieben>",
      "restbestand_bleibt": "<restbestand_bleibt>",
      "tuer_schliesst": "<tuer_schliesst>"
    },
    "name": "kuehlschrank_kaltes_fach_grosse_schale_ablagebelegung"
  }
}

Input Schema

NameRequiredDescriptionDefault
tuer_schliesstYesDie Tür schließt mit genau dieser gleichzeitigen Belegung und ohne Gegenstand im Dichtbereich.
restbestand_bleibtYesDie zweite Ablage im benötigten Höhenbereich bleibt mit dem normalen restlichen Inhalt nutzbar.
schale_einschiebenYesDie größte eigene Schale kann in der notwendigen Lage vollständig in die Kühlablage geschoben werden.
gleiche_ablagenstellungYesDie Beobachtungen stammen aus demselben Aufbau mit beiden Dingen gleichzeitig oder einer überprüften maßgleichen Stellprobe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 the safety profile is covered. Beyond that the description adds only the assertion that the layout must be a single witnessed setup — which the schema already encodes in 'gleiche_ablagenstellung' — and says nothing about how the three tri-state parameters are combined, what happens with 'offen' values, or what the output looks like.

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?

The definition is a single long sentence in two languages whose English half largely re-translates the German half; the core condition is not front-loaded. It is not bloated, but the bilingual duplication and nested clauses cost readability without adding information.

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?

Four required parameters, three of them enums, with no output schema — so the description must at least convey what the agent receives back and how conflicting tri-state values are resolved. It does not, though the fully documented schema keeps this from being inadequate.

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 each of the four parameters carries a precise German description, so the schema does the heavy lifting. The description adds no extra meaning about the tri-state semantics ('belegt'/'ausgeschlossen'/'offen') or about how the boolean gate interacts with the other three, so baseline 3 applies.

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 German clause names a concrete check ('Prüft die praktisch nutzbare Kühlablage für eine große Schale') with two named conditions (occupied second shelf, remaining contents must stay), and the English tail restates it as 'Check simultaneous tray and shelf use'. However the phrasing is circumlocutory ('praktisch nutzbare', 'in one witnessed refrigerator layout') and never states plainly what kind of result — verdict, feasibility flag, capacity value — the check produces, so an agent cannot cleanly separate this from the many other refrigerator-inspection siblings.

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 dependent clause 'wenn der restliche Kühlschrankinhalt bleiben soll' hints at a precondition, but there is no explicit when-to-use statement, no when-not-to-use case, and no pointer to a sibling for the related but different checks (e.g. loading order or door-opening routines). The agent gets scenario colour but no routing guidance.

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