Skip to main content
Glama

getecoback-raumklima

kuehlfach_flaechenprobe_mischbehaelter_zwischenraum

Read-only

Auf einer vorhandenen Ablage zugeschnittene, für Luftwege reservierte Fläche vom nutzbaren Rest trennen — Compare usable shelf footprint after a separately reserved gap.

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": {
      "ablage_cm2": "<ablage_cm2>",
      "bleibt_frei_cm2": "<bleibt_frei_cm2>",
      "bedarf_geplant_cm2": "<bedarf_geplant_cm2>",
      "aufstellung_erprobt": "<aufstellung_erprobt>"
    },
    "name": "kuehlfach_flaechenprobe_mischbehaelter_zwischenraum"
  }
}

Input Schema

NameRequiredDescriptionDefault
ablage_cm2YesTatsächlich gemessene gesamte ebene Ablagefläche in cm².
bleibt_frei_cm2YesLaut bestehender dokumentierter Aufstellung freizuhaltende Fläche in cm².
bedarf_geplant_cm2YesGemessene Stellfläche der passend geprüften Behälter in cm².
aufstellung_erprobtYesKollisionen, Form und freizuhaltende Luftwege sind in dieser konkreten Ablage geprüft.

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. The description adds the domain behavior that a reserved air-path strip is carved out before the usable remainder is compared, but it does not state what the comparison returns, nor what happens when aufstellung_erprobt is false — no output schema exists to answer that.

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 a single compact sentence with an English gloss, so it is short and front-loaded with the core operation. The bilingual duplication is mildly redundant, and the German clause order ('Auf einer vorhandenen Ablage zugeschnittene ... Fläche') is dense, but nothing is padded.

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?

For a four-parameter computation with no output schema, the description should say what the result represents (a delta, a pass/fail, a remaining area) and how aufstellung_erprobt gates the outcome. Neither is covered, leaving the agent able to construct the call but not to interpret or justify its result.

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 all four parameters are already documented and the baseline is 3. The description only loosely hints at ablage_cm2 ('vorhandene Ablage') and bleibt_frei_cm2 ('für Luftwege reservierte Fläche') and adds no arithmetic or unit conventions beyond the schema's cm² definitions.

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 concrete operation: separating a reserved air-path area from the usable remainder of an existing shelf, i.e. comparing usable footprint after a gap is set aside. The verb+resource pair is specific enough for an agent to recognize the tool's job, but it never contrasts this with the other kuehlfach siblings (Behältertausch, Reserveplätze, Auffindprobe), so the domain boundary must be inferred from the name and parameters.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. that measurements must exist before calling), and no named alternative among the numerous sibling tools. The phrase 'Auf einer vorhandenen Ablage' implies the shelf must already exist, but that is context, not 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