Skip to main content
Glama

getecoback-raumklima

fensterplatte_lagertiefe_mit_oder_ohne_adapter

Read-only

Berechnet die nötige Lagertiefe einer ausgebauten Platte bei zwei dokumentierten Adapterzuständen — Compare storage depth with a removable outlet adapter attached or separately packed.

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": {
      "platte_mm": "<platte_mm>",
      "adapter_ueberstand_mm": "<adapter_ueberstand_mm>",
      "huellenraum_mm": "<huellenraum_mm>",
      "fach_mm": "<fach_mm>",
      "abnahme_dokumentiert": "<abnahme_dokumentiert>"
    },
    "name": "fensterplatte_lagertiefe_mit_oder_ohne_adapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
fach_mmYesFreie Tiefe des trockenen Lagerfachs in mm.
platte_mmYesGrößte gemessene Dicke der Platte ohne Adapter in mm.
huellenraum_mmYesGesamtes zusätzliches Platzmaß für die vorgesehene Hülle in mm.
abnahme_dokumentiertYesIst die getrennte Lagerung des Adapters dokumentiert möglich?
adapter_ueberstand_mmYesGemessener zusätzlicher Überstand des eingesetzten Adapters in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 known and the description does not contradict it. Beyond that, the description adds almost nothing: it does not say that the result is a pure computation, what the returned value represents or its units, or how the "dokumentiert" flag changes the outcome.

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 short, but it spends half its length on an English sentence that only paraphrases the German one, and the phrase "bei zwei dokumentierten Adapterzuständen" stays abstract rather than stating the rule. Useful content is front-loaded, yet a third of the text is redundant translation.

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?

All five parameters are required and well documented in the schema, and there is no output schema to explain. However, for a calculation tool the description never states what the computed result looks like or how the two adapter states map to the inputs, leaving that to inference.

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 five parameters (including the boolean abnahme_dokumentiert) are already documented in the schema. The description names no parameters and adds no interpretation beyond the schema, which is the baseline 3 case when structured data carries the semantics.

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 German clause uses a specific verb plus resource ("Berechnet die nötige Lagertiefe einer ausgebauten Platte") and names the distinguishing condition (two documented adapter states), which matches the tool name's "mit oder ohne Adapter". The English half restates the same idea less precisely, but the core purpose is unambiguous.

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 choose this tool over any alternative, nor any prerequisite or exclusion. The only hint is "bei zwei dokumentierten Adapterzuständen", which describes the calculation domain rather than usage context; nothing tells the agent when this is the right call versus the sibling acceptance/inspection tools.

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