Skip to main content
Glama

getecoback-raumklima

kuehlschrank_einraeumfolge

Read-only

Kaltlagerung vorbereiten, damit warme Behälter und lange Türöffnungszeiten nicht zusammenfallen — Prepare a refrigerator loading sequence from container state and available space.

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": {
      "behaelter_warm": "<behaelter_warm>",
      "platz_vorbereitet": "<platz_vorbereitet>",
      "zugriff_blockiert": "<zugriff_blockiert>"
    },
    "name": "kuehlschrank_einraeumfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
behaelter_warmYesUnter den vorgesehenen Behältern ist mindestens einer noch warm?
platz_vorbereitetYesAblageplätze wurden bereits zugeordnet?
zugriff_blockiertYesBeim Einräumen müssten weitere Behälter zuerst umgestellt werden?

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 does not contradict it — planning a loading order is consistent with a read-only tool. It adds the intent behind the ordering (avoiding warm-container/door-open collisions) but says nothing about what the produced sequence looks like, whether it is deterministic, or how partial inputs are handled.

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 definition is short and front-loads the purpose before the English restatement. The German and English halves are near-duplicates, so a portion of the text is redundant rather than additive, which keeps it just short of a 5.

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?

With only three required booleans and no output schema, the description needs to carry the result semantics itself, and it does not — an agent knows it should produce a loading sequence but not its form or granularity. The input side is fully covered by the schema, so the remaining gap is the unspecified output.

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 coverage is 100%, so the three booleans are already fully documented and the baseline is 3. The description gestures at two of them ('container state' and 'available space') but adds no interpretation for the third, zugriff_blockiert, nor any rule about how the flags combine into an ordering decision.

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 states a concrete verb and artifact: prepare a refrigerator loading sequence derived from container state and available space. It is clearly a planning/ordering task rather than a measurement or logging task, but it never contrasts itself with nearby tools such as the temperature protocol or door-opening tool, so differentiation is left to inference.

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?

The opening clause gives a rationale for when this applies (avoid warm containers coinciding with long door-open times), which implies the usage scenario. There is no explicit when-not guidance and no named alternative for the adjacent cases an agent might confuse this with, so guidance stays implied rather than stated.

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