Skip to main content
Glama

getecoback-raumklima

nachtkuehlung_handoff_raumwerte_zeitbezug

Read-only

Wähle bei wechselnder Belegung für jeden Raum die passgenaue nächtliche Temperaturablesung — Select night readings using the actual occupancy handoff

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": {
      "belegungswechsel_min": "<belegungswechsel_min>",
      "messung_a_min": "<messung_a_min>",
      "messung_b_min": "<messung_b_min>",
      "a_c": "<a_c>",
      "b_c": "<b_c>",
      "maximaler_abstand_min": "<maximaler_abstand_min>"
    },
    "name": "nachtkuehlung_handoff_raumwerte_zeitbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cYesGemessene Temperatur in Raum A
b_cYesGemessene Temperatur in Raum B
messung_a_minYesZeit des eingegebenen Raum-A-Werts
messung_b_minYesZeit des eingegebenen Raum-B-Werts
belegungswechsel_minYesZeitpunkt des Wechsels von Raum A nach Raum B im Nachtprotokoll
maximaler_abstand_minYesGrößter Zeitabstand zum Wechsel, der für diese Beobachtung gelten soll

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; the description adds no behavioral context beyond that. It does not explain how ties are broken, whether an out-of-tolerance observation is rejected or clamped, or what the response contains — all critical for a computation with a tolerance parameter.

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 short sentence, which is efficient, but the German/English duplication repeats the same content without adding information, and the key outcome is neither front-loaded nor stated. Nothing is wasted in length, but the content density is low.

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?

With six required parameters, no output schema, and an algorithmic selection rule involving a tolerance threshold, the description should explain the selection logic and result shape. Instead it restates the gist, leaving an agent unable to predict what a call returns or how failures manifest.

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 coverage is 100%, so all six parameters are already documented in the schema, and the baseline is 3. The description's phrase 'für jeden Raum' loosely reinforces the paired A/B structure but adds no meaning about how belegungswechsel_min, messung_a_min/messung_b_min and maximaler_abstand_min interact to produce a result.

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 specific action ('Wähle ... die passgenaue nächtliche Temperaturablesung') and a condition (wechselnde Belegung / occupancy handoff), so the general intent is inferable. However, it never says what is actually selected or returned (one value per room? a boolean? the nearest measurement?), leaving the core operation ambiguous for a tool whose name promises a time-reference computation.

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?

The only guidance is the implied precondition of an occupancy change between room A and room B. There is no statement of when to prefer this over other reading-selection approaches, no prerequisites, and no mention of what to do when the time distance exceeds the supplied maximum.

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