Skip to main content
Glama

getecoback-climate-weather

mikrowelle_deckelgriff_lichte_hoehe_tuerdurchlass

Read-only

Die Gefäßhöhe mit Deckel und Griff an Türöffnung und tatsächlicher Stellposition abgleichen — Check vertical passage and in-use lid clearance.

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": {
      "gefaess_mit_deckel_mm": "<gefaess_mit_deckel_mm>",
      "freie_oeffnung_mm": "<freie_oeffnung_mm>",
      "freie_hoehe_im_garraum_mm": "<freie_hoehe_im_garraum_mm>",
      "gemessen": "<gemessen>"
    },
    "name": "mikrowelle_deckelgriff_lichte_hoehe_tuerdurchlass"
  }
}

Input Schema

NameRequiredDescriptionDefault
gemessenYesEinsetzweg und Stellposition am Gerät gemessen, statt aus Nennvolumen abgeleitet?
freie_oeffnung_mmYesKleinste gemessene freie Öffnung beim Einsetzen in mm.
gefaess_mit_deckel_mmYesGrößte Höhe samt Deckelgriff in mm.
freie_hoehe_im_garraum_mmYesFreie lichte Höhe über der tatsächlichen Stellfläche in mm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that this is a comparison/check based on measurements at the door and actual position, but it does not state what the check returns, how tolerances are handled, or what happens when dimensions fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence, front-loaded with the German check and followed by a concise English gloss. No redundant setup or filler.

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 required parameters and safety annotations are present, and the purpose is clear. However, for a read-only validation tool with no output schema, the definition does not explain the result—e.g., pass/fail, clearance margin, or failure conditions—so an agent knows what to expect only partially.

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 schema already defines all four parameters. The description reinforces that 'Gefäßhöhe mit Deckel und Griff' is compared with door opening and in-use height, but it adds no format, unit, measurement, or boolean-semantics detail beyond the schema.

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 uses a specific verb ('abgleichen' / 'Check') and names the exact resource: vessel height including lid handle against the door opening and actual placement height. It is clearly a vertical-clearance check, though it does not explicitly distinguish itself from nearby microwave-vessel checks.

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?

It implies the use case—verifying that a lidded vessel can pass through the door and fit at the real placement position—but gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. Given the crowded sibling set, this is only minimally adequate.

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