Skip to main content
Glama

getecoback-raumklima

gefrierschrank_zaehler_reset_downtime_energieluecke

Read-only

Trenne beim Zählerreset zwei belegte Gefrierphasen von einem ungemessenen Wiederanlauf — Account for a freezer energy logging gap after a meter reset

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": {
      "davor_kwh": "<davor_kwh>",
      "danach_kwh": "<danach_kwh>",
      "unterbrechung_min": "<unterbrechung_min>",
      "davon_stromlos_belegt_min": "<davon_stromlos_belegt_min>",
      "gleiche_steckdose_nur_geraet": "<gleiche_steckdose_nur_geraet>"
    },
    "name": "gefrierschrank_zaehler_reset_downtime_energieluecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
davor_kwhYesBereits gesicherte Energie vor dem Reset
danach_kwhYesAb späterer stabiler Zähleraufzeichnung erneut gesicherte Energie
unterbrechung_minYesUnprotokollierte Dauer vom Ende der alten bis zum Start der neuen Zählerreihe
davon_stromlos_belegt_minYesTeil der Lücke, der unabhängig nachweisbar ohne Versorgung war
gleiche_steckdose_nur_geraetYesBeide Messdateien gehören zum gleichen Gerät und Verbrauchsumfang

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 the safety profile is covered. The description adds only a restatement of the name's concept and says nothing about how the split is decided, what happens when the documented-offline minutes exceed the gap, or what is returned.

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 (German plus an English gloss) with no filler, front-loading the core distinction. It is efficient, though the bilingual duplication does not add new information for an agent that reads either language.

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?

This is a five-required-parameter computation tool with no output schema, so the description carries the burden of explaining the result. It omits what the return value is, how conflicting inputs (e.g. davo_stromlos_belegt_min > unterbrechung_min) are treated, and what the caller should do with the answer.

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 one of the five parameters documented in-schema (units, bounds, meaning). The description adds no parameter-level meaning or interaction rules beyond the schema, so the baseline of 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 the domain operation (separating two documented freezer phases from an unmeasured restart after a meter reset) but never states what the tool actually produces or what 'Trenne' means operationally. It is more specific than the name alone, yet an agent cannot tell from this text whether it returns a split kWh value, a validity verdict, or a corrected record.

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 guidance, no preconditions, and no mention of any alternative. Close siblings such as gefrierschrank_stromausfall_dauer_zwischen_ankern and abtauereignis_energie_lueckenfreie_zuordnung are not referenced, so routing must be inferred from the name alone.

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