Skip to main content
Glama

getecoback-climate-weather

heizwaesche_teilprotokoll_zusatzgeraet_subtraktion

Read-only

Bei gemeinsamer Messung die nicht getrennt erfasste Hilfsphase offen lassen — Recover only the provably attributable share of a mixed-device drying meter log.

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": {
      "zaehler_und_geraete_belegt": "<zaehler_und_geraete_belegt>",
      "gesamt_kwh": "<gesamt_kwh>",
      "rack_sicher_kwh": "<rack_sicher_kwh>",
      "hilfe_sicher_kwh": "<hilfe_sicher_kwh>"
    },
    "name": "heizwaesche_teilprotokoll_zusatzgeraet_subtraktion"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_kwhYesGemessene Summe der beiden Geräte über das ganze Fenster.
rack_sicher_kwhYesDirekt und separat belegter Teil der Rack-Energie.
hilfe_sicher_kwhYesDirekt und separat belegter Teil der Hilfsenergie.
zaehler_und_geraete_belegtYesIst belegt, dass nur die beiden genannten Geräte im Gesamtzähler erfasst wurden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a safe read-only, closed-world operation, so the description's main added value is the conservative stance: an unrecorded auxiliary phase is left open rather than allocated. That is genuinely useful behavioral context beyond the annotations, but it is stated as a cryptic imperative and says nothing about what is returned or how the boolean evidence flag changes behavior.

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?

Very short with no filler, and the constraining condition is front-loaded. The cost is structural: the German clause and the English sentence partly restate the same idea in two languages, which reads as duplicated rather than complementary and slightly obscures the core instruction.

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?

All four required parameters are covered by the schema, which keeps this adequate. However, with no output schema the description should say what a caller receives (a residual figure? a flagged gap?), and it never resolves whether "offen lassen" means an omitted field or a computed zero-inference result — a meaningful omission for a computation tool.

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 coverage is 100%, so all four parameters are already documented in the schema itself; the description adds only the framing that the total covers both devices over the same window. No formula, precedence, or unit/validation nuance is added beyond what the schema provides, so the baseline 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 (mixed-device drying meter log) and the goal (recover only the provably attributable share), which is more specific than the name alone. But it never states the actual operation or result — nothing says a subtraction of the separately evidenced shares is performed or what the caller gets back — so the purpose stays oblique and is not cleanly distinguished from the many other heizwaesche analysis tools.

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?

"Bei gemeinsamer Messung" implies the triggering condition: readings taken jointly rather than per-device. Beyond that trigger there is no explicit when-not, no prerequisites, and no named alternative among the many sibling heizwaesche tools, so routing is left largely to inference.

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