Skip to main content
Glama

getecoback-raumklima

raumgeraetekombination_zwei_zielquoten

Read-only

Zwei gemessene Betriebsvarianten mit je zwei tatsächlich erreichten Raumzielen auswerten — Compare energy only across modes meeting both measured room outcomes.

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_komfort_h": "<a_komfort_h>",
      "b_komfort_h": "<b_komfort_h>",
      "a_feuchte_h": "<a_feuchte_h>",
      "b_feuchte_h": "<b_feuchte_h>",
      "ziel_beide_h": "<ziel_beide_h>",
      "a_wh": "<a_wh>",
      "b_wh": "<b_wh>",
      "fenster_und_ort_gleich": "<fenster_und_ort_gleich>"
    },
    "name": "raumgeraetekombination_zwei_zielquoten"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_whYesEnergie der vollständigen Variante A.
b_whYesEnergie der vollständigen Variante B.
a_feuchte_hYesStunden im eigenen Feuchtezielband unter A.
a_komfort_hYesKomfortstunden im Temperaturzielband unter Variante A.
b_feuchte_hYesStunden im Zielband unter B.
b_komfort_hYesKomfortstunden im Zielband unter Variante B.
ziel_beide_hYesGeforderte Stunden je Ziel, getrennt bewertet.
fenster_und_ort_gleichYesSind Dauer, Messeinstellungen, Raumaufgabe und Ausgangsbedingungen vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false. The description adds the key selection rule that energy comparison applies only when both room outcomes are met, but it omits return behavior, handling of non-qualifying variants, and how comparability is enforced.

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 front-loaded sentence with no filler, so the core action and condition are immediately visible. The German/English mixing is compact but slightly reduces readability, keeping it below 5.

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?

The core comparison condition is present and annotations cover the safety profile, but with eight required parameters and no output schema, the description does not explain what an evaluation returns or how fenster_und_ort_gleich affects execution. It is adequate but leaves important behavioral details to inference.

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%, so the baseline is 3. The description adds relational meaning beyond the per-parameter descriptions by making clear that energy values are compared only when both target quotas are satisfied, linking a_wh/b_wh to ziel_beide_h and the comfort/humidity hours.

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?

States a specific analytical action (auswerten / compare energy) and a specific resource (two measured operating variants with two achieved room targets). It is clear but does not name or differentiate from any sibling tool, so it stops short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear usage condition: compare energy only across modes that meet both measured room outcomes. It does not say when not to use the tool or name an alternative, so it is not fully explicit about routing.

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