Skip to main content
Glama

getecoback-raumklima

betriebszustand_funktionsbedarf_watt_rang_sperre

Read-only

Herstellerwerte erst dann für eine Auswahl lesen, wenn die tatsächlich benötigte dokumentierte Funktion im betreffenden Zustand verfügbar ist — Compare candidate state values only among confirmed adequate modes.

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>",
      "a_funktion": "<a_funktion>",
      "b_funktion": "<b_funktion>",
      "aufgabe_und_modell_gleich": "<aufgabe_und_modell_gleich>"
    },
    "name": "betriebszustand_funktionsbedarf_watt_rang_sperre"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wYesDem belegten Zustand A zugeordneter Herstellerwert.
b_wYesDem belegten Zustand B zugeordneter Herstellerwert.
a_funktionYesDieselbe notwendige Funktion ist im Zustand A laut Modellbeleg verfügbar?
b_funktionYesDieselbe notwendige Funktion ist im Zustand B laut Modellbeleg verfügbar?
aufgabe_und_modell_gleichYesWerte und Funktionsauskunft betreffen dasselbe Gerät und dieselbe tatsächlich benötigte Aufgabe?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuine validity constraint beyond the annotations – restrict comparison to confirmed adequate modes – but is silent on what the tool does when a_funktion/b_funktion are 'nein' or 'offen' and on what it reports back, which is the behaviourally interesting part.

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?

It is short and the gating condition is front-loaded before the action, which is good structure. However, the English clause after the dash largely restates the German clause, so half the text is duplication rather than new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter read-only comparison tool with no output schema, the definition supplies the essential decision rule: only compare values across states whose required function is confirmed. The remaining gap is the return value – with no output schema, the description should say what the comparison yields – which is a moderate omission rather than fatal.

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 required parameters are already documented in the schema, making 3 the baseline. The description reinforces the two gating parameters (documented function availability per state, same task/device check) but adds no format, ordering, or interpretation detail beyond what the schema states.

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 names a resource (Herstellerwerte / candidate state values) and an action (lesen / compare) plus a gating condition, so the intent is partly visible. But the actual operation – what a 'Auswahl' is, what the comparison produces, and what the 'Rang/Sperre' in the name means – is never stated, so an agent cannot confidently predict the result. It also offers no differentiation from the many other betriebszustand_* siblings.

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?

It gives an explicit precondition for use: read/compare values only when the actually needed documented function is available in the relevant state, and compare only among confirmed adequate modes. That is a real when-to-use rule and an implicit when-not (values for inadequate modes must not be compared). There is no named alternative tool or exclusion for the remaining edge cases (e.g. function 'offen'), which keeps it below a 5.

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