Skip to main content
Glama

getecoback-climate-weather

monoblock_kuehlunterbrechung_restzeit_unbekannt

Read-only

Bilanziert protokollierte Kühlzeit, Fensterunterbrechung und Bedienpausen mit separat ungeklärter Restzeit — Account for recorded cooling, window interruptions and user pauses with an unknown remainder.

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": {
      "beobachtet_min": "<beobachtet_min>",
      "gekuehlt_min": "<gekuehlt_min>",
      "fensterunterbrechung_min": "<fensterunterbrechung_min>",
      "bedienpause_min": "<bedienpause_min>"
    },
    "name": "monoblock_kuehlunterbrechung_restzeit_unbekannt"
  }
}

Input Schema

NameRequiredDescriptionDefault
gekuehlt_minYesDarin belegter Kühlbetrieb in Minuten.
beobachtet_minYesGesamtdauer des einheitlich geführten Protokolls in Minuten.
bedienpause_minYesWeitere belegte manuelle Pause ohne Überlappung in Minuten.
fensterunterbrechung_minYesDavon getrennt protokollierte Unterbrechung am Fenster in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 semantics are covered. The description adds the key behavioral concept that the output is a separately unclarified remainder, which is genuinely useful. It does not state what happens if the supplied minutes exceed the total observed duration, whether negative remainders are possible, or how the result is presented.

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?

One front-loaded sentence that states the accounting inputs before the residual outcome. The German/English duplication is mildly redundant but serves cross-language robustness at low cost. No filler or vague clauses.

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 four-required-parameter computation tool with no output schema, the definition should make the return value explicit; it only alludes to an 'unknown remainder' without saying it is returned, its unit, or its sign convention. Inputs are fully covered by the schema, so the gap is confined to the output side.

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 every parameter documented in German including units (Minuten) and a 0–1440 bound, so the schema already carries the burden. The description reiterates the same three components plus the derived remainder but adds no format, ordering, or constraint detail beyond the schema. Baseline 3 is appropriate.

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 operation ('Bilanziert' / 'Account for') over specific quantities: recorded cooling time, window interruption, user pause, and a separately unclarified remainder. This is more than a restatement of the name, and an agent can infer it computes a residual balance. It does not, however, contrast itself with related monoblock siblings such as the cooling-rate or observation-record tools, so differentiation is missing.

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 explicit when-to-use or when-not-to-use guidance and no named alternative, even though several sibling tools deal with overlapping cooling protocol data. Usage is only inferable from the required inputs (all four minute values must be supplied). The agent is left to deduce that the tool should be chosen when a discrepancy must be reconciled.

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