Skip to main content
Glama

getecoback-raumklima

backofen_zweiblech_einstellkorridor

Read-only

Zwei vorgegebene Einstellbereiche für einen gemeinsamen Backofenlauf schneiden — Find the overlapping permitted settings for a one-chamber tray plan.

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": {
      "a_min_c": "<a_min_c>",
      "a_max_c": "<a_max_c>",
      "b_min_c": "<b_min_c>",
      "b_max_c": "<b_max_c>",
      "gleicher_modus": "<gleicher_modus>",
      "zwei_bleche_erlaubt": "<zwei_bleche_erlaubt>"
    },
    "name": "backofen_zweiblech_einstellkorridor"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_max_cYesOberer dokumentierter Sollwert für Aufgabe A.
a_min_cYesUnterer dokumentierter Sollwert für Aufgabe A.
b_max_cYesOberer dokumentierter Sollwert für Aufgabe B.
b_min_cYesUnterer dokumentierter Sollwert für Aufgabe B.
gleicher_modusYesBeide Aufgaben erlauben denselben Ofenmodus.
zwei_bleche_erlaubtYesGleichzeitige Nutzung zweier Ebenen ist für Gerät und Abläufe bestätigbar.

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 establish readOnlyHint=true and openWorldHint=false, so the agent knows this is a side-effect-free, closed computation. The description adds the useful framing that only 'vorgegebene' / 'dokumentierte' values are considered, but it says nothing about how a non-overlapping result is signalled, or how the two boolean feasibility flags (gleicher_modus, zwei_bleche_erlaubt) gate or alter the returned corridor.

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 compact sentence with the operation front-loaded, no filler, and no restatement of the title. The German and English halves are near-duplicates, which costs a little density but aids comprehension of an otherwise jargon-heavy name.

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 pure arithmetic tool with full schema coverage the description covers the core, but there is no output schema, and the description never indicates what the computation returns (lower/upper intersected bounds, an empty result, or a feasibility verdict from the booleans). That is the one gap an agent would most likely need closed before calling.

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%: all six parameters carry their own German descriptions, including the bounds and the meaning of the two boolean feasibility checks. The description adds no syntax, ordering, or interpretation beyond what the schema already states, so the baseline of 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 operation ("Einstellbereiche ... schneiden") on a specific resource (two documented temperature corridors feeding one shared oven run), so an agent can tell this is a range-intersection computation rather than a lookup or a write. It does not name or contrast any sibling tool, and the jargon-heavy bilingual phrasing ('Einstellkorridor', 'one-chamber tray plan') leaves the exact output object slightly opaque.

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?

Usage is implied rather than stated: 'für einen gemeinsamen Backofenlauf' signals the tool applies when two tasks must share one chamber, which is a usable trigger condition. There is no explicit when-not, no mention of what to do when the corridors are disjoint, and no alternative named for single-task or multi-chamber planning.

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