Skip to main content
Glama

getecoback-raumklima

punktwaerme_anzahl_arbeitszyklen_nutzbar

Read-only

Aus einem protokollierten Wärmefenster bestimmen, wie viele vollständige Arbeitsschritte nach persönlicher Vorbereitung und vor Aufräumen hineinpassen — Count full attended work units with fixed use-specific overhead.

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": {
      "passend_zusammenhaengend_min": "<passend_zusammenhaengend_min>",
      "vorbereiten_min": "<vorbereiten_min>",
      "abschluss_min": "<abschluss_min>",
      "stueck_min": "<stueck_min>",
      "geplanter_bedarf": "<geplanter_bedarf>"
    },
    "name": "punktwaerme_anzahl_arbeitszyklen_nutzbar"
  }
}

Input Schema

NameRequiredDescriptionDefault
stueck_minYesGemessene Dauer je vollständig erledigtem, gleichartigem Schritt.
abschluss_minYesDarin vor dem Ende für den Abschluss reservierte Zeit.
vorbereiten_minYesDarin zuerst nötige Vorbereitungsminuten am Platz.
geplanter_bedarfYesAnzahl tatsächlich benötigter Schritte.
passend_zusammenhaengend_minYesBereits gemessener durchgehender Zeitraum am genutzten Platz mit passender Wärme.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered; the description usefully adds that the overhead is fixed and that preparation precedes and cleanup trails the counted units. It does not disclose the crucial behavioral detail for a counting tool: whether partial units are rounded up or floored, and what is returned when the window is too short for even one unit.

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 core operation is front-loaded in a single well-built German clause, followed by a compact English restatement. The bilingual duplication is mild redundancy but aids cross-lingual routing; nothing else is wasted.

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

Completeness4/5

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

With no output schema, the description's job is to convey what comes back; it conveys the conceptual output (a count of full work units) adequately. It is slightly incomplete because it never states the output type or the shortfall behavior, though the mathematical framing is clear enough for correct invocation.

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 five parameters are self-documenting and the baseline is 3. The description adds slight semantic value by establishing the ordering of vorbereiten_min (first) and abschluss_min (reserved before the end) as subtracted overhead, but it never explains how geplanter_bedarf interacts with the computed count, leaving the cap semantics to the schema alone.

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 operation: determine how many complete work units fit into a logged heat window, net of setup and cleanup time. Verb plus resource are both explicit and the computation's scope is unambiguous. It stops short of naming any sibling to contrast with, which keeps it at 4 rather than 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?

Usage is implied by the opening clause ('Aus einem protokollierten Wärmefenster bestimmen'), so an agent can infer the precondition of an already-measured window. However, there is no explicit when-not guidance (e.g. when a continuous-phase or spare-capacity sibling would be the correct choice) and no named alternative, which matters given the very large sibling set.

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