Skip to main content
Glama

getecoback-climate-weather

waermelogger_heizphase_setzwert_anteile

Read-only

Teile eine Heizbeobachtung an einem protokollierten Sollwertwechsel in zwei Auswertungsphasen — Split a heating observation at a documented setpoint change

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": {
      "fenster_start_min": "<fenster_start_min>",
      "wechsel_min": "<wechsel_min>",
      "fenster_ende_min": "<fenster_ende_min>",
      "soll_vorher_c": "<soll_vorher_c>",
      "soll_nachher_c": "<soll_nachher_c>"
    },
    "name": "waermelogger_heizphase_setzwert_anteile"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechsel_minYesMinute, in der der Sollwert nachweisbar geändert wurde
soll_vorher_cYesAlter dokumentierter Sollwert
soll_nachher_cYesNeuer dokumentierter Sollwert
fenster_ende_minYesEnde des Messfensters
fenster_start_minYesBeginn des betrachteten Messfensters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world operation, so safety behavior is largely covered. The description adds the high-level behavior of splitting into two evaluation phases, but it does not explain output shape, boundary handling, or how the window and setpoint-change parameters interact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single, front-loaded sentence with no filler. The German/English duplication is an exact translation, but the overall wording remains compact and easy to scan.

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?

The core action is understandable and the parameter schema is complete, which covers much of what an agent needs. However, with no output schema, the description does not explain what the returned phases contain or how edge cases are handled.

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?

All five parameters are fully documented in the schema, including their ranges and meanings, so schema coverage is 100%. The description adds no parameter-specific meaning beyond what the schema already provides, making the baseline 3 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 gives a specific verb and resource: split a heating observation at a documented setpoint change into two evaluation phases. It is clear what the tool does, but it does not differentiate itself from any sibling tool or name an alternative.

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?

The description states the operation but gives no explicit when-to-use guidance, prerequisites, exclusions, or alternatives. The condition 'at a documented setpoint change' is embedded in the purpose rather than presented as selection guidance.

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