Skip to main content
Glama

getecoback-climate-weather

heissluft_trennwand_umruestfenster

Read-only

Freie Pause für den dokumentierten Wechsel zwischen geteilter und gemeinsamer Schublade prüfen — Reserve an idle slot for a documented divider reconfiguration.

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": {
      "entnehmbare_trennung": "<entnehmbare_trennung>",
      "frei_ab_min": "<frei_ab_min>",
      "naechste_nutzung_min": "<naechste_nutzung_min>",
      "vorbereiten_min": "<vorbereiten_min>",
      "umruesten_min": "<umruesten_min>"
    },
    "name": "heissluft_trennwand_umruestfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_ab_minYesMinute ab Planbeginn, ab der die gesamte Schublade unbelegt ist.
umruesten_minYesEigene Dauer für das Umrüsten nach der vorgesehenen Anleitung.
vorbereiten_minYesEigene Dauer inklusive der in der Anleitung geforderten Vorbereitung.
entnehmbare_trennungYesDie Anleitung der genauen Variante bestätigt die entnehmbare Trennwand.
naechste_nutzung_minYesMinute ab Planbeginn, ab der die nächste Aufgabe die Schublade braucht.

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 the safety profile is covered. The description adds almost nothing beyond that: it does not say whether infeasibility is reported as a value or an error, what the returned window looks like, or how the durations are combined. The word 'Reserve' also sits uneasily with readOnlyHint=true, since reserving normally implies allocation — the description should have clarified that this is a feasibility check rather than an actual booking.

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 good, but the German and English halves restate each other with slightly different verbs ('prüfen' vs 'Reserve') instead of the English half adding precision. Density is high but at the cost of clarity rather than in service of it.

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 five required parameters and no output schema, the description should explain what the tool returns — a feasibility verdict, a time window, a boolean — and it does not. For a planning/checking tool whose entire value is the result, that leaves a material 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% with five well-documented numeric/boolean parameters, so the schema already carries the semantics. The description contributes no additional meaning about how 'frei_ab_min', 'vorbereiten_min' and 'umruesten_min' interact, so the baseline of 3 applies.

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 resource area ('geteilte und gemeinsame Schublade') and an action ('Freie Pause ... prüfen' / 'Reserve an idle slot'), but the verb is ambiguous — check versus reserve — and the domain jargon ('dokumentierter Wechsel zwischen geteilter und gemeinsamer Schublade') makes it hard to say precisely what is computed. It does not distinguish itself from near-siblings such as 'heissluft_schubladenpause_zonenzeit', so an agent must guess which one applies.

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?

There is no statement of when to call this tool, when not to, or which sibling handles the adjacent case. The only implicit cue is that the operation concerns divider reconfiguration windows, which is closer to context than 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