Skip to main content
Glama

getecoback-raumklima

induktion_gefaessgriffe_kalte_aussenkontur_probe

Read-only

Prüfe eine dokumentierte Kaltprobe auf überlappende Außenkonturen entlang einer geraden Trennlinie, nachdem die Böden den Zonen zugeordnet sind — Evaluate the observed cold side-by-side footprint including handles

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": {
      "trennabstand_mm": "<trennabstand_mm>",
      "erster_ueberstand_mm": "<erster_ueberstand_mm>",
      "zweiter_ueberstand_mm": "<zweiter_ueberstand_mm>",
      "eigener_mindestabstand_mm": "<eigener_mindestabstand_mm>",
      "kontur_in_gemeinsamer_linie": "<kontur_in_gemeinsamer_linie>"
    },
    "name": "induktion_gefaessgriffe_kalte_aussenkontur_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
trennabstand_mmYesGemessener Abstand der beiden Gefäßmitten entlang der betrachteten geraden Linie
erster_ueberstand_mmYesReichweite von Mitte A nach B, einschließlich Griff, in exakt der beobachteten Ausrichtung
zweiter_ueberstand_mmYesReichweite von Mitte B nach A, einschließlich Griff, in exakt der beobachteten Ausrichtung
eigener_mindestabstand_mmYesGewünschter rein geometrischer Zwischenraum, kein Sicherheitsabstand
kontur_in_gemeinsamer_linieYesBeide Reichweiten liegen auf demselben relevanten Streifen; bei seitlich versetzten Griffen erst Kaltprobe nachsehen

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?

With readOnlyHint=true and openWorldHint=false already covering safety, the description usefully adds that this evaluates an already documented cold trial (observed geometry, not a live measurement). It never says what a call yields — a verdict, a clearance figure, or overlapping ranges — and no output schema compensates.

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?

A single front-loaded German clause states the check plus its precondition, followed by a short English gloss. The bilingual pairing is slightly redundant but compact, with no filler sentences.

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?

For a five-required-parameter geometric check with no output schema, the description covers the input side adequately via schema richness but omits the result side entirely. An agent knows how to call it but not what it will learn.

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 the five parameters are already fully documented. The description reinforces the central idea (handles included, straight dividing line, prior zone assignment) but adds no format or interpretation guidance 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 names a specific check: overlapping outer contours along a straight dividing line between two cookware footprints, including handles. It is clearly distinct from a generic zone-assignment tool, though it never names a sibling to route away to.

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 gives a sequencing precondition — run this after the pot bases have been assigned to zones — which implies usage context. It does not state when the check is unnecessary, nor name an alternative tool for the preceding or adjacent steps.

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