Skip to main content
Glama

getecoback-raumklima

heissluft_unterbrechungsfreies_programmfenster

Read-only

Ein laut Anleitung ununterbrochenes Heißluftprogramm zwischen zwei festen Küchenbelegungen einpassen. — Fit a documented uninterrupted cycle between two fixed kitchen uses.

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": {
      "luecke_vorher_min": "<luecke_vorher_min>",
      "luecke_nachher_min": "<luecke_nachher_min>",
      "startvorbereitung_min": "<startvorbereitung_min>",
      "programm_min": "<programm_min>",
      "vorgaben_bestaetigt": "<vorgaben_bestaetigt>"
    },
    "name": "heissluft_unterbrechungsfreies_programmfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
programm_minYesEigene gemessene Dauer des unverändert vorgesehenen Programms.
luecke_vorher_minYesZusammenhängend freie Zeit vor der anderen Nutzung.
luecke_nachher_minYesZusammenhängend freie Zeit nach der anderen Nutzung.
vorgaben_bestaetigtYesSind Aufstellung, Programm und Belegung für genau dieses Modell geklärt?
startvorbereitung_minYesZuvor am selben Platz erforderliche Vorbereitungszeit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. The description adds that the cycle is documented and uninterrupted and that it sits between two fixed uses, but it does not state what result is produced (feasibility, window, schedule) or what happens when the cycle does not fit, leaving behavioral output unclear especially since no output schema exists.

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 German sentence is front-loaded and compact, but the subsequent English translation duplicates the same content without adding information. The bilingual structure is understandable but not maximally efficient; every sentence does not earn its place when the second is a direct translation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-parameter computation tool with no output schema, so the description carries the burden of explaining the return value or feasibility result. It does not say whether the tool returns a window, a boolean fit, or an error when the program does not fit, leaving a meaningful gap for an agent trying to interpret the outcome.

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?

With 100% schema description coverage across all five required parameters, the schema already explains each field in detail. The description adds no additional meaning about how the gap, preparation, and program durations are combined, so the baseline of 3 is appropriate.

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 states a specific verb ('einpassen' / fit) and a concrete resource ('ununterbrochenes Heißluftprogramm zwischen zwei festen Küchenbelegungen'). It is distinguishable from the many heissluft_* siblings because it is the only one framed as fitting a cycle between two fixed uses, but it does not explicitly name or contrast any sibling.

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: use this when a documented uninterrupted hot-air cycle must be placed between two fixed kitchen uses. There is no explicit when-not guidance, no prerequisite check outside the 'vorgaben_bestaetigt' parameter, and no alternative named for cases where the user wants a different scheduling question answered.

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