Skip to main content
Glama

getecoback-raumklima

geraetegruppe_gemeinsamer_vorlauf_auftragswechsel

Read-only

Energie eines tatsächlich gemeinsam nutzbaren Vorlaufs von zwei vollständigen Einzelstarts bei gleichem Ergebnis abgrenzen — Compare a batched workflow with duplicated preparation overhead.

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": {
      "getrennt_a_wh": "<getrennt_a_wh>",
      "getrennt_b_wh": "<getrennt_b_wh>",
      "gruppen_vorlauf_wh": "<gruppen_vorlauf_wh>",
      "gruppen_nach_vorlauf_wh": "<gruppen_nach_vorlauf_wh>",
      "ergebnis_gleich": "<ergebnis_gleich>"
    },
    "name": "geraetegruppe_gemeinsamer_vorlauf_auftragswechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
getrennt_a_whYesVollständiger Verbrauch des getrennten Auftrags A mit eigener Vorbereitung.
getrennt_b_whYesVollständiger Verbrauch des getrennten Auftrags B mit eigener Vorbereitung.
ergebnis_gleichYesIdentische vollständige Leistung beider Abläufe und bestätigter gemeinsamer Vorlauf?
gruppen_vorlauf_whYesGemessener einmaliger gemeinsamer Vorbereitungsteil im zweiten Ablauf.
gruppen_nach_vorlauf_whYesAlle weiteren gemessenen Wh bis zu beiden fertigen Aufträgen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 agent knows this is a closed, side-effect-free computation. The description adds the conceptual framing of what is being compared, but says nothing about behavior on the precondition failure (what happens when ergebnis_gleich is false) or what kind of result is produced. With annotations carrying the safety profile, this is adequate but thin.

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

Conciseness3/5

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

It is a single sentence plus a short English gloss, so there is little waste. But the German clause is dense and the English gloss only paraphrases the framing rather than stating the operation or return value, so the structure does not front-load the actionable part.

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?

There is no output schema, yet the description never indicates what is returned — a Wh delta, a ratio, a boolean verdict — for a tool whose entire value is its computed result. It also omits the handling of the ergebnis_gleich precondition. For a five-required-parameter calculation tool this leaves a material gap.

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% — all five parameters carry their own German descriptions, including units (Wh) and roles for the separate runs versus the grouped run. The tool description adds no parameter-level meaning beyond that, 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 a concrete operation (demarcating the genuinely shareable preparation energy of two full individual runs against a grouped run) and its English gloss points at 'batched workflow vs duplicated preparation overhead'. However, it never says plainly that the tool computes a comparison figure, and it does not differentiate itself from nearby siblings such as strommessung_gemeinsamer_offset_differenz or geraetegruppe_energievorteil_verbrauchsmaterial_ausgleich, which sound like they address adjacent comparison questions.

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 explicit when-to-use statement and no alternatives named. The clause 'bei gleichem Ergebnis' hints at a precondition (identical output required for the comparison to be valid), but this is left implicit and the caller must infer it. No guidance on when this comparison is inapplicable.

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