Skip to main content
Glama

getecoback-climate-weather

heizprofil_zwei_vereinbarte_sollbereiche

Read-only

Zwei gleichzeitige Sollwertwünsche auf eine dokumentiert auswählbare gemeinsame Stellung prüfen — Check whether two agreed thermostat preference ranges share an available setpoint.

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_min": "<a_min>",
      "a_max": "<a_max>",
      "b_min": "<b_min>",
      "b_max": "<b_max>",
      "vorhandener_sollwert": "<vorhandener_sollwert>"
    },
    "name": "heizprofil_zwei_vereinbarte_sollbereiche"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_maxYesObere akzeptierte Einstellung der Person A in °C.
a_minYesUntere akzeptierte Einstellung der Person A in °C.
b_maxYesObere akzeptierte Einstellung der Person B in °C.
b_minYesUntere akzeptierte Einstellung der Person B in °C.
vorhandener_sollwertYesEine laut Gerät tatsächlich auswählbare Einstellung in °C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 notion of a "documented selectable" position; with no output schema it still never says what the check returns (boolean? the shared value? the overlap interval?), which is the single most important behavioral fact for a predicate tool.

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 a single front-loaded sentence, but the German half is dense and nearly unintelligible ("auf eine dokumentiert auswählbare gemeinsame Stellung"), and the English gloss restates rather than clarifies. The bilingual duplication consumes space without adding information.

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

Completeness2/5

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

For a five-required-parameter predicate with no output schema and no annotations describing results, the description should explain the decision rule and the return shape. It omits both, leaving the role of vorhandener_sollwert and the meaning of a positive/negative outcome undefined.

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 including units (°C) and bounds are already documented; baseline 3 applies. The description adds no meaning beyond what the schema gives — it does not explain the relationship between the four range bounds and the existing setpoint, which is exactly the semantic an agent would need.

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 check ("prüfen") over two agreed setpoint ranges, which is more than the opaque tool name provides, and the English gloss helps. However, the core semantics stay fuzzy: it never states whether the criterion is simply that the two ranges intersect, or that the intersection must contain the caller-supplied selectable setpoint ("vorhandener_sollwert"). An agent cannot predict the verdict logic from this wording.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus a plain range-intersection or any sibling tool, and no prerequisites or exclusions. Usage is implied only by the word "prüfen".

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