Skip to main content
Glama

getecoback-raumklima

punktwaerme_durchgehende_arbeitsphase_nachweis

Read-only

Ein Wärmefenster auf durchgehend nutzbare Dauer prüfen, auch wenn die Gesamtdauer groß genug erscheint — Distinguish a usable uninterrupted comfort run from summed fragmented minutes.

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": {
      "gesamt_geeignet_min": "<gesamt_geeignet_min>",
      "laengster_geeigneter_block_min": "<laengster_geeigneter_block_min>",
      "benoetigt_am_stueck_min": "<benoetigt_am_stueck_min>",
      "protokoll_lueckenlos": "<protokoll_lueckenlos>"
    },
    "name": "punktwaerme_durchgehende_arbeitsphase_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_geeignet_minYesSumme aller beobachteten getrennten Zeiträume mit für die Person passender Wärme.
protokoll_lueckenlosYesIst die Reihenfolge einschließlich möglicher kurzer Unterbrechungen vollständig erfasst?
benoetigt_am_stueck_minYesSelbst festgelegte, tatsächlich benötigte Dauer ohne Unterbrechung.
laengster_geeigneter_block_minYesLängster ohne Unterbrechung am Platz beobachteter geeigneter Block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety is covered and the description's job is to add judgment behavior. It does add the key behavioral idea that a large total may still fail the check, but it never says what the tool returns or how 'protokoll_lueckenlos=false' changes the verdict, leaving the outcome logic undisclosed.

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 check condition is front-loaded and the sentence is short, but the trailing English clause ('Distinguish a usable uninterrupted comfort run from summed fragmented minutes') restates the same idea already conveyed in German, adding length without 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?

With four required numeric/boolean parameters and no output schema, the description should at least convey the shape of the verdict and the role of the gap-free-protocol flag. It conveys the decision rule but leaves the result and the effect of incomplete logging unexplained, so an agent knows when to call it but not fully what to expect.

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 all four parameters are already documented, including the distinction between 'gesamt_geeignet_min' (sum of separate periods) and 'laengster_geeigneter_block_min' (longest uninterrupted block). The description reinforces that distinction conceptually but adds no new constraint, unit, or interaction 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 specific verb and object ('Ein Wärmefenster auf durchgehend nutzbare Dauer prüfen') and states the discriminating question: usable uninterrupted run versus summed fragmented minutes. An agent can tell what the tool concludes, though it never names a concrete sibling tool that handles the fragmented-total case.

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 clause 'auch wenn die Gesamtdauer groß genug erscheint' gives an implicit trigger: call this when a summed duration looks sufficient and you must verify it is uninterrupted. There is no explicit when-not guidance, no named alternative tool, and no stated prerequisites such as the protocol needing to be gap-free.

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