Skip to main content
Glama

getecoback-climate-weather

arbeitsplatz_technik_waerme_nach_pause_aufbauklasse

Read-only

Bei der Rückkehr an den Arbeitsplatz warmen Gerätebereich und weiterhin warme Raumluft mit unabhängigen Referenzen trennen — Label local hardware warmth after an observed pause without inferring room cooldown.

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": {
      "geraetenah_c": "<geraetenah_c>",
      "sitz_c": "<sitz_c>",
      "raum_referenz_vorher_c": "<raum_referenz_vorher_c>",
      "vergleichsgrenze_k": "<vergleichsgrenze_k>"
    },
    "name": "arbeitsplatz_technik_waerme_nach_pause_aufbauklasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
sitz_cYesZeitgleicher Luftwert am Sitzplatz.
geraetenah_cYesLuftwert nahe dem Gerät zum Ende der protokollierten Pause.
vergleichsgrenze_kYesEigene kleinste unterscheidbare Differenz in K.
raum_referenz_vorher_cYesBelegter Referenzwert am Sitzplatz vor der zugehörigen Arbeitsphase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 the safety profile is covered. The description adds a genuine interpretive constraint — it labels local hardware warmth and explicitly refuses to conclude anything about room cooldown — which is useful behavioral context, but it does not describe how the result is expressed.

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 sentence with no padding, but the em-dash construction and the bilingual framing ('Bei der Rückkehr ... — Label ...') make it denser and less front-loaded than it needs to be for a four-parameter read tool.

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 no output schema and four required numeric inputs, the description never tells the agent what comes back or how a comparison outcome is represented. The 'do not infer room cooldown' caveat is the only completeness-bearing statement; the rest of the interpretive burden is left open.

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 each of the four numeric inputs is already documented. The description's phrase 'unabhängigen Referenzen' loosely gestures at why both a device-near value and a prior seat reference are supplied, but adds no units, tolerances, or interpretation 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 a recognizable operation — separating device-adjacent warmth from still-warm room air using independent references after a pause. But the verb is metaphorical ('trennen', 'Label') and never states concretely what the tool produces (a classification? a boolean? a note?), so an agent knows the theme more than the action.

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 precondition 'after an observed pause' and the exclusion 'without inferring room cooldown' give a small hint about when it applies, but there is no guidance on when to pick this over the many sibling workplace-warmth tools and no stated prerequisites for the reference values.

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