Skip to main content
Glama

getecoback-raumklima

monoblock_kuehlprobe_betrieb_nach_startphase

Read-only

Trennt den gemessenen Zeitraum vor stabilem Kühlbetrieb von der nutzbaren Beobachtungszeit — Separate observed startup from the later stable measurement window.

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": {
      "protokoll_min": "<protokoll_min>",
      "anlauf_min": "<anlauf_min>",
      "kuehlbetrieb_belegt": "<kuehlbetrieb_belegt>",
      "gewuenscht_min": "<gewuenscht_min>"
    },
    "name": "monoblock_kuehlprobe_betrieb_nach_startphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
anlauf_minYesZeit bis zum beobachteten regulären Kühlbetrieb oder bis zum Ende in Minuten.
protokoll_minYesGesamtdauer einer beendeten Beobachtung ab regulärem Start in Minuten.
gewuenscht_minYesSelbst gewählte Dauer für eine vergleichbare Messung nach dem Anlauf in Minuten.
kuehlbetrieb_belegtYesWar der Beginn des Kühlbetriebs anhand der Anzeige oder Protokollangabe belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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, but the description adds no behavioral context beyond restating its own purpose in two languages. It does not disclose edge-case handling that clearly matters here (e.g., what happens when kuehlbetrieb_belegt is false, or when anlauf_min exceeds protokoll_min) nor what the result looks like.

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 single sentence is front-loaded and free of padding, but roughly half its length is a verbatim English translation of the German clause, which adds no new information for an agent reading both. It is short but partly redundant rather than dense with value.

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?

There is no output schema, so the description carries the burden of explaining what a 'separation' returns — a split of minutes, a boolean, or a derived comparison — and it does not. Combined with missing applicability guidance for a four-required-parameter computation with clear validity conditions, the definition is under-specified for its complexity.

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 in the schema with units and bounds. The description contributes no additional meaning about individual parameters, not even clarifying how 'gewuenscht_min' relates to the separated usable window, 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 an operation ('Trennt ... von ...' / 'Separate ... from ...') on two identifiable quantities: the pre-stable-startup interval and the usable observation window. However, it stays abstract about what is actually produced (a duration split? a minute count? a report?) and gives no differentiation from the many closely named 'monoblock_*' and 'fenster_*' measurement siblings, so an agent cannot confidently classify it without reading the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of the prerequisite that the observation must actually be concluded (implied only by the schema's 'beendete Beobachtung'), and no alternative tool is named. The agent must infer applicability purely from parameter names.

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