Skip to main content
Glama

getecoback-raumklima

nachtlueftung_auswahl_mit_schliesspuffer

Read-only

Wählt aus zwei bereits gemessenen kühlen Zeitabschnitten, die einen nötigen Puffer zum Fensterschluss enthalten — Compare two sampled cool periods with an explicit time allowance for closing.

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": {
      "abschnitt_a_min": "<abschnitt_a_min>",
      "abschnitt_b_min": "<abschnitt_b_min>",
      "schliesspuffer_min": "<schliesspuffer_min>",
      "ziel_offen_min": "<ziel_offen_min>"
    },
    "name": "nachtlueftung_auswahl_mit_schliesspuffer"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_offen_minYesGewünschte durchgehende Öffnungszeit in Minuten.
abschnitt_a_minYesVerfügbare Zeit im zuerst beobachteten geeigneten Abschnitt in Minuten.
abschnitt_b_minYesVerfügbare Zeit im zweiten geeigneten Abschnitt in Minuten.
schliesspuffer_minYesSelbst gewählte Zeit für reguläres Schließen in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 agent knows this is a side-effect-free local computation. The description reinforces that inputs are pre-measured periods and that a buffer is factored in, but it does not disclose the outcome shape (which segment is returned, or what a no-fit result looks like) and there is no output schema to fill that gap.

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 bilingual sentence with the core concept (two measured periods plus a closing buffer) front-loaded and no filler. The German/English duplication adds length but also aids disambiguation, so it is only a minor cost.

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 small read-only comparison tool with fully documented parameters this is close to adequate, but the missing decision rule and return behavior leave a real gap since there is no output schema to compensate. An agent could call it with correct arguments but could not predict or interpret the result confidently.

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%, with each of the four minute-based parameters clearly documented including bounds. The description only echoes the role of the closing buffer, adding no units, rounding, or interaction semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action (choosing between two already-measured cool periods) and the resource (two time segments with a closing buffer). However, it never states the actual decision rule — e.g. whether a segment is selected when its duration covers ziel_offen_min plus schliesspuffer_min — so the agent knows the topic but not precisely what the tool decides.

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 phrase 'aus zwei bereits gemessenen ... Zeitabschnitten' implies the precondition that measurements already exist and that this is a downstream selection step, which is useful implied guidance. It does not explicitly say when to prefer this over sibling measurement tools or what happens if neither segment qualifies.

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