Skip to main content
Glama

getecoback-raumklima

geraetegruppe_getrennte_geraetezahl_schattenkosten

Read-only

Bei zwei in derselben Zeitspanne abgeschlossenen Reihen prüfen, ob der kleinere Einzellastverbrauch durch mehr Gerätezeit erkauft wird — Compare metered energy with measured occupied device-minutes.

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_wh": "<a_wh>",
      "b_wh": "<b_wh>",
      "a_geraeteminuten": "<a_geraeteminuten>",
      "b_geraeteminuten": "<b_geraeteminuten>",
      "gleicher_zeitrahmen": "<gleicher_zeitrahmen>"
    },
    "name": "geraetegruppe_getrennte_geraetezahl_schattenkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_whYesVollständige beobachtete Energie des Ablaufs A.
b_whYesEntsprechend gemessene Energie von B.
a_geraeteminutenYesSummierte belegte Minuten aller eingesetzten Geräte in A.
b_geraeteminutenYesSummierte belegte Minuten aller eingesetzten Geräte in B.
gleicher_zeitrahmenYesGleiche Aufgabenzahl und gleiche verstrichene Kalenderdauer in beiden Abläufen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/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. Beyond that the description adds only the comparison idea; it does not say what happens when gleicher_zeitrahmen is false, whether the check still returns a result or signals invalidity, or what form of answer comes back despite there being no output schema.

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?

A single short sentence with the core question front-loaded, which is efficient. However, the German sentence and its English paraphrase are largely duplicative, and neither adds detail the other lacks, so the bilingual restatement spends words without adding information.

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 pure five-parameter computation tool with no output schema, the description should indicate the shape of the result and how the boolean precondition affects the answer. It establishes the comparison concept but leaves the return value and invalid-input behavior unexplained, which is a meaningful gap for a tool with no output schema.

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 (a_wh, b_wh, a_geraeteminuten, b_geraeteminuten, gleicher_zeitrahmen) are already documented in the schema. The description adds the conceptual linkage between energy and device-minutes but no format, units, or boundary guidance 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 frames the tool as a check ("prüfen, ob ...") comparing metered energy against occupied device-minutes, which conveys the analytical intent. But it never says what the tool actually produces (a verdict, a ratio, shadow-cost figure?) and the opaque compound name is not decoded, so an agent cannot confidently distinguish its output from sibling comparison 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?

It states a precondition: two series completed within the same time span. It does not state when this tool should be chosen over sibling comparison tools, nor any when-not conditions or prerequisites beyond the shared time frame, which the gleicher_zeitrahmen parameter already handles.

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