Skip to main content
Glama

getecoback-climate-weather

kueche_messprotokoll_gemeinsamer_zaehler_zwei_pausen

Read-only

Zwischen zwei belegten Arbeitsabschnitten prüfen, ob beide Verbrauchswerte aus gemeinsamen kumulativen Ablesungen trennbar sind — Derive nonoverlapping kitchen-use segments from an intact meter reading sequence.

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": {
      "start_wh": "<start_wh>",
      "zwischen_a_wh": "<zwischen_a_wh>",
      "zwischen_b_wh": "<zwischen_b_wh>",
      "ende_wh": "<ende_wh>",
      "selbe_skala": "<selbe_skala>"
    },
    "name": "kueche_messprotokoll_gemeinsamer_zaehler_zwei_pausen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_whYesAblesung nach Ende des zweiten Abschnitts.
start_whYesAbgelesener kumulativer Messwert vor dem ersten Abschnitt in Wh.
selbe_skalaYesMessgerät, Zählerstandsskala und Zeitachse blieben unverändert.
zwischen_a_whYesAblesung direkt nach dem Ende des ersten Abschnitts.
zwischen_b_whYesAblesung nach der gemeinsamen Pause und vor dem zweiten Abschnitt.

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 safety profile is covered, and the description is consistent with a pure computation over readings. However, it is ambiguous whether the tool returns a separability verdict or actually derives the segment values ('prüfen, ob ... trennbar' vs 'derive nonoverlapping segments'), and it says nothing about failure behavior when readings are not separable or the sequence is not intact.

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 split across German and English, with the scenario condition front-loaded and no filler. The bilingual duplication is mildly redundant since the English half mostly restates the German, but it is compact and well ordered.

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 five-parameter read-only computation there is no output schema, so the description is the only place to explain what an agent gets back — a boolean separability result, derived segments, or an error case — and it leaves this ambiguous. The input side is adequately covered by the schema plus the description's note about shared cumulative readings.

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 every one of the five parameters is documented in the schema itself, making 3 the baseline. The description reinforces the semantics that the readings are cumulative and must come from one intact sequence, which supports the selbe_skala flag, but adds no ordering, unit, or consistency constraints beyond that.

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 (prüfen/derive whether both consumption values are separable into non-overlapping kitchen-use segments from cumulative readings) rather than restating the tool name. An agent can tell it is a computational/validation tool over a meter sequence. It does not distinguish itself from the many structurally similar siblings (e.g. warmwasser_erholung_zwei_gepruefte_pausen), so it stops short of a 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?

The applicability condition is implied by 'Zwischen zwei belegten Arbeitsabschnitten' — the tool fits the case of two occupied segments separated by a shared pause on one meter. There is no explicit when-not guidance, no mention of an alternative tool, and no statement about preconditions such as the readings needing to be on the same scale (only indirectly hinted by 'intact meter reading sequence').

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