Skip to main content
Glama

getecoback-climate-weather

gruppenmessung_zwei_geraeteraten_identifizierbar

Read-only

Zwei unbekannte mittlere Geräteraten aus zwei Messfenstern mit verschiedenem Zeitmix auflösbar prüfen — Solve a two-window mixing model only when the operating profiles differ enough.

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": {
      "a_fenster_eins_h": "<a_fenster_eins_h>",
      "b_fenster_eins_h": "<b_fenster_eins_h>",
      "a_fenster_zwei_h": "<a_fenster_zwei_h>",
      "b_fenster_zwei_h": "<b_fenster_zwei_h>",
      "fenster_eins_wh": "<fenster_eins_wh>",
      "fenster_zwei_wh": "<fenster_zwei_wh>",
      "raten_konstant_annahme": "<raten_konstant_annahme>"
    },
    "name": "gruppenmessung_zwei_geraeteraten_identifizierbar"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_eins_whYesGemeinsame aktive Energie beider Geräte ohne belegte Hintergrundenergie.
fenster_zwei_whYesGemeinsame aktive Energie ohne Hintergrundenergie im zweiten Fenster.
a_fenster_eins_hYesAktive Stunden von Gerät A im ersten Fenster.
a_fenster_zwei_hYesAktive Stunden von A im zweiten Fenster.
b_fenster_eins_hYesAktive Stunden von Gerät B im ersten Fenster.
b_fenster_zwei_hYesAktive Stunden von B im zweiten Fenster.
raten_konstant_annahmeYesIst die Annahme unveränderter Geräteraten und Linearität begründet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description adds that this is a solvability check on a linear mixing model with a constancy assumption, but says nothing about what is returned when the system is singular or ill-conditioned.

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?

A single front-loaded sentence with the core condition stated up front; the German/English duplication is mildly redundant but the English clause does sharpen the modal 'only when differ enough'.

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?

Parameters and safety are well covered, but with no output schema the description should state what the check returns (resolvable rates vs. an error/indeterminate result); that gap matters for a computational tool the agent must interpret.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with per-parameter German descriptions, so the baseline is 3; the description goes slightly beyond by framing the two window parameters as a shared time mix and tying the boolean to the constant-rate/linearity assumption's justification.

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 operation: checking whether two unknown mean device rates are resolvable from two measurement windows with differing time mixes. A two-window mixing model is concrete and distinguishable from unrelated siblings, though it does not explicitly separate itself from the similarly named 'gruppenmessung_stichprobe_anteil_betriebsprofile'.

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?

It gives a usage precondition ('only when the operating profiles differ enough'), which implies when the model is valid, but 'differ enough' is left unquantified and no alternative tool is named for the case where profiles are too similar.

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