Skip to main content
Glama

getecoback-raumklima

raumgeraete_heizen_kuehlen_gegenarbeit_messung

Read-only

Gleichzeitig gemessene Heiz- und Kühlwirkung im selben Kontrollraum als thermische Gegenarbeit aufschlüsseln — Quantify balanced opposing thermal output during one verified overlap window.

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": {
      "heiz_abgegeben_kwh": "<heiz_abgegeben_kwh>",
      "kuehl_abgefuehrt_kwh": "<kuehl_abgefuehrt_kwh>",
      "zusammen_strom_kwh": "<zusammen_strom_kwh>",
      "gemeinsame_raumgrenze": "<gemeinsame_raumgrenze>"
    },
    "name": "raumgeraete_heizen_kuehlen_gegenarbeit_messung"
  }
}

Input Schema

NameRequiredDescriptionDefault
heiz_abgegeben_kwhYesGemessene abgegebene Wärme ausschließlich im Überlappungsfenster.
zusammen_strom_kwhYesGemessener Stromverbrauch beider Geräte im selben Fenster.
kuehl_abgefuehrt_kwhYesGemessene abgeführte Wärme ausschließlich im selben Fenster.
gemeinsame_raumgrenzeYesBetreffen die Wärmemengen denselben abgeschlossenen Messbereich, ohne Latentwärme oder doppelte Messung?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the constraint of one verified overlap window and balanced opposing thermal output, but it does not explain what the breakdown returns or how the computation handles edge cases.

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?

The description is short and front-loads the core purpose and measurement condition. The bilingual repetition is mildly redundant but does not obscure the main point.

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 four required parameters are fully described in the schema and the description supplies the key domain constraint of a verified overlap window. With no output schema, though, the description should say more about what the thermal counterwork breakdown produces.

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 the four parameters are already well documented. The description reinforces the shared measurement window and same-room condition but adds no parameter-specific syntax or interpretation beyond the 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 names a specific action (aufschlüsseln/quantify) and resource (simultaneous heating and cooling effect as thermal counterwork) in one control room. It is clear enough to distinguish from generic measurement tools, but it does not explicitly differentiate itself from related siblings such as raumgeraete_komfortquote_schnittmenge_band.

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?

Use is implicitly scoped to simultaneous heating and cooling measurements within the same verified overlap window and room boundary. However, there is no explicit when-not guidance or named alternative, so the agent must infer the selection conditions.

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