Skip to main content
Glama

getecoback-raumklima

querlueften_koordination_zwei_bedienfenster

Read-only

Mit einer Person je Fenster nach getrennter Vorbereitung das gemeinsame Lüftungsfenster finden — Find a coordinated cross-ventilation slot after separate opening preparations.

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_bereit_min": "<a_bereit_min>",
      "b_bereit_min": "<b_bereit_min>",
      "a_spaetestens_zu_min": "<a_spaetestens_zu_min>",
      "b_spaetestens_zu_min": "<b_spaetestens_zu_min>",
      "gemeinsam_gewuenscht_min": "<gemeinsam_gewuenscht_min>"
    },
    "name": "querlueften_koordination_zwei_bedienfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_bereit_minYesA ist nach allen vorbereitenden Schritten am ersten Fenster ab dieser Minute bereit.
b_bereit_minYesB ist am zweiten Fenster ab dieser Minute bereit, jeweils auf derselben Zeitachse.
a_spaetestens_zu_minYesSpätestens zu dieser Minute muss das Fenster A geschlossen sein.
b_spaetestens_zu_minYesSpätestens zu dieser Minute muss das Fenster B geschlossen sein.
gemeinsam_gewuenscht_minYesSelbst festgelegte gemeinsame Dauer, ohne wissenschaftliche Zielvorgabe.

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. The description adds the separate-preparation context but does not explain result handling, infeasible cases, or how conflicts are resolved; behavior is only partially disclosed.

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?

The definition is a single compact bilingual sentence with the scenario and action front-loaded. The German and English restate the same idea, which is mildly redundant, but there is no filler or buried lead.

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 read-only scheduling computation with rich input schema and annotations, the description is sufficient to identify the task. However, with no output schema, it does not state what the tool returns (e.g., a common slot or failure result), leaving a meaningful completeness gap.

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%, and each of the five required minute parameters is documented in the schema. The description adds no parameter-level detail beyond the schema, so 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 concrete action (find a coordinated cross-ventilation slot) and the scenario (one person per window after separate preparation), so the resource and intent are clear. It does not explicitly contrast with any sibling tool, which keeps it from a 5.

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 tool is for coordinating two windows with one person each after preparation, but gives no explicit when-to-use/when-not conditions, prerequisites, or named alternatives among the many sibling planners. The use case is inferable but not operational guidance.

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