Skip to main content
Glama

getecoback-climate-weather

arbeitsplatz_raumwechsel_persoenliche_hitzepause

Read-only

Bei einem bestätigten Hitzefenster prüfen, ob ein vorübergehender Raumwechsel genug ungestörte Arbeitszeit lässt — Check productive time left after a temporary heat-driven desk move.

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": {
      "hitze_ab": "<hitze_ab>",
      "hitze_bis": "<hitze_bis>",
      "hinweg_und_aufbau": "<hinweg_und_aufbau>",
      "rueckweg_und_abbau": "<rueckweg_und_abbau>",
      "arbeitsblock_min": "<arbeitsblock_min>",
      "ausweichraum_erprobt": "<ausweichraum_erprobt>"
    },
    "name": "arbeitsplatz_raumwechsel_persoenliche_hitzepause"
  }
}

Input Schema

NameRequiredDescriptionDefault
hitze_abYesBeginn der aus eigener Beobachtung geplanten Ausweichzeit.
hitze_bisYesEnde der geplanten Ausweichzeit am selben Tag.
arbeitsblock_minYesGewünschte zusammenhängende Arbeitszeit in Minuten.
hinweg_und_aufbauYesGemessene Minuten für Hinweg und nutzbaren Aufbau.
rueckweg_und_abbauYesGemessene Minuten für Abbau und Rückweg.
ausweichraum_erprobtYesIst die verfügbare Ausweichfläche für diese Aufgabe bei vergleichbaren Bedingungen erprobt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 useful decision context (confirmed heat window, temporary move, productive time check) but says nothing about the nature of the result, determinism, or how the check is evaluated.

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?

It is a single, front-loaded sentence that states the trigger before the check. The bilingual dash construction is slightly awkward but does not waste space.

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 six required parameters are documented in the schema, and the description supplies the usage trigger. However, with no output schema, it does not explain what the check returns (boolean, remaining minutes, or a structured assessment), leaving a meaningful gap for an agent invoking it.

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 well documented in the schema. The description does not add meaning beyond those field descriptions; baseline 3 is appropriate.

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 states a specific verb ('prüfen') and a concrete decision object: whether a temporary heat-driven desk move leaves enough uninterrupted working time. It is clear what the tool computes, but it does not explicitly differentiate itself from the many other 'raumwechsel' siblings.

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

Usage Guidelines4/5

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

It gives a clear precondition for use: 'Bei einem bestätigten Hitzefenster' (when a heat window is confirmed). It does not name alternatives or state when not to use it, so it falls short of full when/when-not guidance.

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