Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_druckphase_waermeprotokoll

Read-only

Eine lokale Temperaturänderung nur dann separat einem protokollierten Druckfenster gegenüberstellen, wenn PC und Beleuchtung unverändert dokumentiert sind — Isolate a logged printer episode from changes to other desk loads.

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": {
      "drucker_vorher_waerme_c": "<drucker_vorher_waerme_c>",
      "drucker_nachher_waerme_c": "<drucker_nachher_waerme_c>",
      "pc_und_bildschirm_unveraendert": "<pc_und_bildschirm_unveraendert>",
      "licht_und_sonne_unveraendert": "<licht_und_sonne_unveraendert>",
      "druckereignis_belegt": "<druckereignis_belegt>"
    },
    "name": "arbeitsplatz_druckphase_waermeprotokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
druckereignis_belegtYesDie Druckphase ist im gleichen Zeitfenster tatsächlich dokumentiert.
drucker_vorher_waerme_cYesMesswert an einem fest markierten lokalen Punkt vor der Druckphase.
drucker_nachher_waerme_cYesMesswert an demselben Punkt nach der definierten Phase.
licht_und_sonne_unveraendertYesKünstliches Licht und Sonne veränderten sich am Messpunkt währenddessen nicht wesentlich.
pc_und_bildschirm_unveraendertYesPC-Arbeitslast und Bildschirmzustand sind währenddessen überwacht und blieben ähnlich.

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?

With readOnlyHint=true and openWorldHint=false already declaring a safe, closed-world read, the description adds one piece of behavioral context: the operation is only meaningful when the control loads are verifiably static. It does not say what the tool produces or how it responds when the gating conditions are false, which matters for a 5-required-parameter call.

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 compact bilingual sentence with no filler, and the gating condition leads. The nested 'nur dann ... wenn' construction is dense but not padded.

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?

All five required parameters are documented in the schema and there is no output schema to explain. However, for a tool whose entire purpose is conditional attribution, the description omits the outcome when preconditions are unmet, leaving a real gap for an agent deciding how to act.

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% and each of the five parameters carries its own German description, so the schema does the heavy lifting. The description reinforces that the booleans act as preconditions, but adds no new detail about units, measurement points, or acceptable tolerance beyond the schema.

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 the domain (a logged printing window vs. local temperature change) but the framing is conditional reasoning ('nur dann ... gegenüberstellen') rather than a concrete verb+resource statement. The English tail 'Isolate a logged printer episode from changes to other desk loads' helps, yet an agent still cannot tell whether the tool records, validates, or merely gates an attribution.

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

Usage Guidelines3/5

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

The description does give an explicit precondition for use: only when PC and lighting are documented as unchanged. It does not mention any alternative sibling tool or what to do when that precondition fails, so guidance is implied rather than complete.

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