Skip to main content
Glama

getecoback-raumklima

gefrierfach_hohe_boxen_flexplatzbedarf

Read-only

Gemessene große und kleine Behälterplätze so zuordnen, dass die nur für hohe Boxen geeigneten Plätze genutzt werden. — Allocate high and short freezer containers across restricted and flexible positions.

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": {
      "hohe_boxen": "<hohe_boxen>",
      "niedrige_boxen": "<niedrige_boxen>",
      "nur_hohe_plaetze": "<nur_hohe_plaetze>",
      "nur_niedrige_plaetze": "<nur_niedrige_plaetze>",
      "flexible_plaetze": "<flexible_plaetze>"
    },
    "name": "gefrierfach_hohe_boxen_flexplatzbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
hohe_boxenYesEinzuordnende gleich hohe hohe Boxen aus derselben Passprobe.
niedrige_boxenYesEinzuordnende gleich niedrige Boxen aus derselben Passprobe.
flexible_plaetzeYesWeitere gleichzeitig nutzbare Plätze, die jeweils eine hohe oder niedrige Box aufnehmen.
nur_hohe_plaetzeYesBestätigte Plätze, in die nach Grundfläche und Höhe nur Boxen der höheren Sorte passen.
nur_niedrige_plaetzeYesBestätigte Plätze, in die nach Grundfläche und Höhe nur Boxen der niedrigeren Sorte passen.

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 nothing behavioral: it does not say what happens when the box counts exceed available positions (error, partial allocation, or success flag), nor what the response contains. For a computation tool with no output schema, that omission is significant.

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 short parallel sentences, German then English, with no filler. The bilingual duplication is mild redundancy but aids robustness, and the core constraint (high-only positions should be used) is front-loaded.

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?

This is a five-required-parameter combinatorial allocation tool with no output schema, so the description is the only place to explain the result shape and edge-case behavior - and it does neither. An agent can form the inputs but cannot anticipate what comes back or how infeasible inputs are handled.

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 every parameter (hohe_boxen, niedrige_boxen, nur_hohe_plaetze, nur_niedrige_plaetze, flexible_plaetze) is documented in the schema itself. The description only restates the high-vs-flexible distinction in general terms and adds no constraints such as mutual exclusivity or how flexible positions are consumed. Baseline 3 is appropriate when the schema carries the semantics.

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 description gives a recognizable verb ('zuordnen'/'allocate') and a resource (high vs. short freezer boxes across restricted and flexible positions), so the allocation intent is visible. However, it never states what the call actually produces - an assignment plan, per-position counts, or a feasibility verdict - which leaves the operation's outcome ambiguous. It also does not differentiate itself from the similarly named sibling gefrierfach_leerbehaelter_rueckstellprobe.

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 statement of when to use this tool, when not to, or which sibling to pick instead. The only hint is the phrase about preferring use of high-only positions, which is a domain constraint rather than invocation guidance. An agent must infer the trigger condition from the parameter list alone.

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