Skip to main content
Glama

getecoback-climate-weather

trockner_zeitfenster_nachlauf_und_raum

Read-only

Vor gemeinsamem Raumwechsel den beobachteten Geräte- und Entnahmenachlauf einzeln zeitlich berücksichtigen. — Keep a shared room reservation separate from a dryer’s automatic and manual occupation.

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": {
      "hauptprogramm_fertig_min": "<hauptprogramm_fertig_min>",
      "automatischer_nachlauf_min": "<automatischer_nachlauf_min>",
      "waesche_entnehmen_min": "<waesche_entnehmen_min>",
      "raum_naechste_nutzung_min": "<raum_naechste_nutzung_min>"
    },
    "name": "trockner_zeitfenster_nachlauf_und_raum"
  }
}

Input Schema

NameRequiredDescriptionDefault
waesche_entnehmen_minYesAnschließend benötigte aktive Minuten für Entnahme und Mitnahme.
hauptprogramm_fertig_minYesBeobachtetes Ende der Hauptphase auf der Minutenachse.
raum_naechste_nutzung_minYesBestätigter Beginn der nachfolgenden Raumnutzung auf derselben Achse.
automatischer_nachlauf_minYesBeobachtete erforderliche Geräte-Nachlaufminuten bis zur möglichen Entnahme.

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 already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world computation with no side effects. The description adds the conceptual framing of keeping reservation and occupation separate, but says nothing about what the tool produces or how the four observed minute values are combined — a gap for a pure computation tool with no output schema.

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?

Two short sentences, but they are a German original and an English rendering that do not say the same thing — the German describes taking after-run and removal time into account individually, while the English talks about keeping a reservation separate. The duplication adds ambiguity rather than reinforcement, and neither sentence is front-loaded with an action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four required numeric inputs with a bounded 0–1440 minute axis and no output schema: the agent can populate the parameters, but the description does not explain what the call returns or how the inputs interact (for example whether the next room use must fall after main phase plus after-run plus removal). For a computation tool with no output schema, that missing result semantics is a meaningful gap.

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 four minute-axis parameters carries its own German explanation, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which is the expected baseline when coverage is complete.

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 conveys the domain concept — separating a dryer's automatic and manual occupation from a shared room reservation — which distinguishes it from generic dryer or laundry siblings. However, it never states the operation itself (compute? check? compare?) or names a resource the tool acts on, so the agent must infer from the name that this evaluates a time window. Concept is clear, the action is not.

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?

'Vor gemeinsamem Raumwechsel' gives a real timing trigger: call this before coordinating a shared room change. That is implied usage context rather than explicit guidance — there are no exclusions, no prerequisites about data availability, and no named alternatives among the many time-window and dryer siblings.

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