Skip to main content
Glama

getecoback-raumklima

stromgruppe_drei_paare_messziel

Read-only

Drei mögliche Gerätepaare gegen ein selbst gewähltes Messziel unter bereits beobachteter Hintergrundlast vergleichen — List the pairs within a budgeting target for interval-average power.

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_w": "<a_w>",
      "b_w": "<b_w>",
      "c_w": "<c_w>",
      "rest_w": "<rest_w>",
      "messziel_w": "<messziel_w>",
      "additiv_belegt": "<additiv_belegt>"
    },
    "name": "stromgruppe_drei_paare_messziel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wYesVergleichbar gemessene mittlere Last von A.
b_wYesMittlere Last von B.
c_wYesMittlere Last von C.
rest_wYesSeparat gemessene zusätzliche Hintergrundlast.
messziel_wYesEigenes Auswertungsziel für die modellierte mittlere Last, kein elektrischer Grenzwert.
additiv_belegtYesSind die Eingaben vom gleichen Messraster und ist eine additive Modellrechnung hier begründet?

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 readOnlyHint=true and openWorldHint=false, so the safe, closed-world read nature is covered. The description adds that the target is a self-chosen evaluation goal under already-observed background load and that the result is a set of pairs within a budgeting target, which is useful. It still does not say how pairs are enumerated or ranked, what 'within budget' means numerically, or the units of the returned values.

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?

One compact sentence with the resource and constraint front-loaded, followed by a short English gloss. The bilingual duplication is mild redundancy but no sentence is wasted, and there is no padding or hedging.

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?

With six required numeric/boolean parameters, no output schema, and no annotations revealing results, the description should at least describe the selection rule and output shape; it only says the pairs are listed within a budgeting target. For a modelling tool whose correctness depends on the additive-model premise, that premise is asserted nowhere visible outside the schema, leaving a real 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%, so every parameter (a_w, b_w, c_w, rest_w, messziel_w, additiv_belegt) is already documented, which sets the baseline at 3. The description only reinforces the framing of rest_w as already-observed background load and messziel_w as a self-chosen goal; it adds no rule tying the six inputs together or explaining how the pairs are formed.

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 German clause names an act ('Drei mögliche Gerätepaare ... vergleichen') and the English gloss names a different framing ('List the pairs within a budgeting target'), so the agent gets a resource (pairs from A/B/C) but an ambiguous verb — comparison report vs. filtered list. There is no differentiation from the many sibling stromgruppe_* tools, so an agent cannot tell which one to pick from the text alone.

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: 'unter bereits beobachteter Hintergrundlast' and 'selbst gewähltes Messziel' sketch the scenario in which the tool applies, but there is no explicit when-to-use, no when-not, and no named alternative among the many siblings. The additive-model precondition surfaces only inside the input schema, not in the description.

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