Skip to main content
Glama

getecoback-raumklima

heizzonen_messpaar_reaktion_zielraeume

Read-only

Bei derselben Wärmeanforderung beobachtete Reaktionen zweier Räume auseinanderhalten — Separate two room temperature responses to the same heating request.

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_vorher": "<a_vorher>",
      "a_nachher": "<a_nachher>",
      "b_vorher": "<b_vorher>",
      "b_nachher": "<b_nachher>",
      "messuneindeutigkeit": "<messuneindeutigkeit>",
      "anforderung_und_zeit_geprueft": "<anforderung_und_zeit_geprueft>"
    },
    "name": "heizzonen_messpaar_reaktion_zielraeume"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vorherYesZimmer A vor der Anforderung.
b_vorherYesZimmer B vor der Anforderung.
a_nachherYesZimmer A am gemeinsamen Messende.
b_nachherYesZimmer B am gemeinsamen Messende.
messuneindeutigkeitYesEigene Grenze für eine unterscheidbare Nettoänderung in °C.
anforderung_und_zeit_geprueftYesWurden Wärmeanforderung und gleiche Messzeit bestätigt?

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 declare readOnlyHint=true and openWorldHint=false, so the agent already knows this is a safe, self-contained computation. The description adds the framing that both rooms must share one heating request and one measurement point, which is genuine context. It does not disclose what happens at the messuneindeutigkeit boundary or what the tool produces, leaving the main behavioral question open.

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?

A single front-loaded sentence with the core operation stated first, and no filler. The bilingual duplication is slightly redundant but aids disambiguation of the German identifiers at minimal cost.

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?

There is no output schema, yet the description never says what is returned — a boolean 'distinguishable' verdict, a per-room delta, or a diagnostic. For a six-required-parameter computation tool whose entire value is the result, that is a significant omission.

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 six parameters are already documented in the schema, and the baseline is 3. The description reinforces the paired-room structure but adds no syntax, units, or interpretation beyond what the schema provides.

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?

The description names a specific operation (separating/auseinanderhalten) on a specific resource (the observed reactions of two rooms to the same heating request). An agent can tell this is a two-room comparison tool, distinct from single-room siblings. It stops short of 5 because the outcome of the separation (a verdict, a delta, a classification) is never stated.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only implicit usage constraint comes from the required boolean 'anforderung_und_zeit_geprueft' in the schema, which the description never mentions or explains.

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