Skip to main content
Glama

getecoback-raumklima

raumluft_messpause_schwellendauer_grenzen

Read-only

Grenze einen durch eine Messpause unterbrochenen warmen Abschnitt ohne Interpolation ein — Bound warm time without filling an interruption in the log

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": {
      "alle_min": "<alle_min>",
      "belegt_zu_warm_min": "<belegt_zu_warm_min>",
      "messluecke_min": "<messluecke_min>",
      "rest_kuehler_bestaetigt": "<rest_kuehler_bestaetigt>"
    },
    "name": "raumluft_messpause_schwellendauer_grenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
alle_minYesDauer des betrachteten Protokollfensters
messluecke_minYesMinuten ohne verwertbare Messung
belegt_zu_warm_minYesProtokollierte Minuten über dem eigenen Vergleichswert aus durchgehend erfassten Abschnitten
rest_kuehler_bestaetigtYesÜbrige Minuten sind laut eigener Protokollregel als höchstens am Vergleichswert belegt

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 agent knows this is a safe, closed-world computation. The description adds the meaningful behavioral fact that the gap is not interpolated, i.e. the result is a conservative bound rather than an estimate. It does not disclose what happens when rest_kuehler_bestaetigt is false (error, rejection, or a reported bound) or what form the bound takes.

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?

Two short clauses with the action front-loaded and the bilingual gloss aiding comprehension of an unusually dense German compound name. No filler sentences, though the German and English restatements are partly redundant.

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 parameters, no output schema, and a purely computational purpose, the description should say what value is returned (a bounded duration? a capped count?) and how the confirmation flag affects the outcome. Those gaps leave an agent unable to predict the result shape, though the input side is fully covered by the schema.

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, including units and ranges. The only added meaning is the 'no interpolation' rule, which implicitly tells the agent that messluecke_min is treated as unmeasured rather than filled. That is useful but modest against a fully documented schema.

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 verb and object: 'Grenze einen ... warmen Abschnitt ... ein' / 'Bound warm time', qualified by the condition that the section is interrupted by a measurement pause. That is far more precise than a tautology, and the 'ohne Interpolation / without filling an interruption' clause pins down the distinguishing characteristic of the computation.

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 rather than stated: an agent can infer this applies when a warm period is split by a logging gap and no interpolation is permitted. There is no explicit when-not guidance, no mention of an alternative bounding or estimating tool, and no prerequisites spelled out.

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