Skip to main content
Glama

getecoback-raumklima

induktion_zwei_gefaesse_exklusive_zonen_belegung

Read-only

Prüfe, ob zwei vorhandene Böden gleichzeitig unterschiedlichen Zonen zugeordnet werden können, wenn eine rechte Verbundzone beide Einzelzonen belegt — Solve a simultaneous two-vessel zone assignment

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": {
      "modell_bestaetigt": "<modell_bestaetigt>",
      "erstes_rechteck": "<erstes_rechteck>",
      "erste_breite_mm": "<erste_breite_mm>",
      "erste_tiefe_mm": "<erste_tiefe_mm>",
      "zweites_rechteck": "<zweites_rechteck>",
      "zweite_breite_mm": "<zweite_breite_mm>",
      "zweite_tiefe_mm": "<zweite_tiefe_mm>",
      "bodenmasse_belegt": "<bodenmasse_belegt>"
    },
    "name": "induktion_zwei_gefaesse_exklusive_zonen_belegung"
  }
}

Input Schema

NameRequiredDescriptionDefault
erste_tiefe_mmYesRechteckige Bodentiefe; bei rundem Boden ignoriert
erste_breite_mmYesGemessen am Boden, runder Durchmesser oder rechteckige Breite
erstes_rechteckYesErstes Gefäß rechteckig; andernfalls rund
zweite_tiefe_mmYesRechteckige Bodentiefe; bei rundem Boden ignoriert
zweite_breite_mmYesGemessen am Boden, runder Durchmesser oder rechteckige Breite
zweites_rechteckYesZweites Gefäß rechteckig; andernfalls rund
bodenmasse_belegtYesMaße und gegebenenfalls Ausrichtung beider Gefäße sind nachvollziehbar
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add operational context. It contributes the central constraint (one combined zone blocking both single zones) but says nothing about what the result expresses, and there is no output schema to fall back on.

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 sentence states the check, followed by a short English gloss and a one-line framing of the task. There is no filler, though the bilingual repetition of the same idea adds minor redundancy rather than new information.

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 tool with eight required parameters and no output schema, the definition never indicates what the response contains (presumably a feasibility verdict, possibly with a reason), nor that model confirmation is a hard prerequisite. The core scenario is covered, but the result contract is left implicit.

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 each of the eight parameters (dimensions, round/rectangular flags, model confirmation, measurement basis) is already documented in the schema. The description adds only that the vessels are "vorhandene Böden", which does not extend parameter meaning beyond the structured data; baseline 3 applies.

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 verb ("Prüfe" / check) and a precise resource scenario: whether two existing vessel bottoms can be assigned to different zones simultaneously when a right-hand combined zone occupies both individual zones. This is far more specific than a restatement of the name. It stops short of a 5 because it does not distinguish itself from near neighbours such as induktion_powerflex_aktivierte_rechte_zonen_beleg.

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?

The condition under which the check applies (a right-hand combined zone covering both single zones) is stated, which implies the usage context. However, there is no explicit when-not-to-use guidance and no named alternative among the many induction-related siblings, so the agent must infer routing.

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