Skip to main content
Glama

getecoback-raumklima

stromgruppe_vier_betriebszustaende_wechselwirkung

Read-only

Gemessene Einzellasten und gemeinsamen Betrieb gegen dieselbe Ruhephase auf Nichtadditivität prüfen — Reconcile all four observed activation states under comparable conditions.

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": {
      "ruhe_wh": "<ruhe_wh>",
      "a_allein_wh": "<a_allein_wh>",
      "b_allein_wh": "<b_allein_wh>",
      "zusammen_wh": "<zusammen_wh>",
      "fenster_gleich": "<fenster_gleich>"
    },
    "name": "stromgruppe_vier_betriebszustaende_wechselwirkung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruhe_whYesGemessene Energie, wenn beide Geräte inaktiv waren.
a_allein_whYesGemessene Energie, nur Gerät A aktiv.
b_allein_whYesGemessene Energie, nur Gerät B aktiv.
zusammen_whYesGemessene Energie, beide Geräte gleichzeitig aktiv.
fenster_gleichYesSind Dauer, Messgrenze und sonstige Nutzung in allen vier Fenstern vergleichbar?

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 readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world computation, so the description's burden is reduced. It adds the analytic intent (non-additivity check against a shared idle baseline) but says nothing about what the computation returns or how the comparability flag affects the result. With no output schema, that omission is the main behavioral gap.

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?

The definition is short and front-loads the analytic goal, which is good. However, the English sentence is a loose paraphrase of the German rather than new information, so roughly half the text is duplicative. Trimming to one precise statement would lose nothing.

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?

For a read-only computation over five fully documented numeric/boolean inputs, the description covers the inputs adequately. The notable gap is the absence of an output schema combined with no description of the return value — an agent cannot tell whether it receives a boolean verdict, a delta, or a structured report. A sentence on the result shape would complete the definition.

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 all five parameters are already self-documenting, which sets the baseline at 3. The description does contribute framing by contrasting 'Einzellasten' with 'gemeinsamen Betrieb' against 'derselben Ruhephase', clarifying that the four energy values must share one baseline. It adds no detail on units, expected magnitude, or the consequence of fenster_gleich being false.

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 German clause names a concrete operation — testing measured individual loads and the combined run against the same idle window for non-additivity — which is more specific than the tool name alone. The English sentence restates it as 'reconcile all four observed activation states,' confirming the verb and object. It does not explicitly distinguish itself from similarly named siblings such as the four-setup interaction tool, keeping it just below a 5.

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?

Usage is only implied: the tool is for the case where four comparable measurements exist and non-additivity is suspected. Nothing states when to prefer a sibling (e.g. the three-pair or unobserved-co-activation variants) or what to do when the comparability flag is false. The agent must infer the routing decision from the parameter names.

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