Skip to main content
Glama

getecoback-climate-weather

dusche_ablauf_hilfe_raumbelegung_puffer

Read-only

Duschzeit, geplante Unterstützung und anschließende Raumfreigabe in einem belegten Zeitfenster abstimmen — Align an assisted shower routine with the room’s booked handover.

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": {
      "raum_ab": "<raum_ab>",
      "raum_bis": "<raum_bis>",
      "hilfe_ab": "<hilfe_ab>",
      "hilfe_bis": "<hilfe_bis>",
      "gemeinsam_min": "<gemeinsam_min>",
      "danach_frei_min": "<danach_frei_min>"
    },
    "name": "dusche_ablauf_hilfe_raumbelegung_puffer"
  }
}

Input Schema

NameRequiredDescriptionDefault
raum_abYesBeginn der alleine für diesen Ablauf verfügbaren Raumzeit.
hilfe_abYesZugesagte Hilfe ab Minute.
raum_bisYesVerbindliches Ende der Raumzeit.
hilfe_bisYesZugesagte Hilfe bis Minute.
gemeinsam_minYesMit der beteiligten Person vereinbarte Dauer, in der beide anwesend sein müssen.
danach_frei_minYesEingeplante Minuten nach dieser Phase bis zur Zimmerfreigabe.

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 safety is covered and the description need not repeat it. Beyond that it adds almost nothing: it does not say what happens when the windows conflict (e.g. hilfe_ab before raum_ab, or gemeinsam_min exceeding the help window), whether it fails or reports a verdict, and with no output schema the return shape is left completely undisclosed.

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 short and front-loads the three coordinated elements, but the English clause is a verbatim translation of the German sentence and contributes no additional information, so not every sentence earns its place.

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 six required parameters, no output schema, and read-only annotations, the description should clarify what the tool returns and which combination of inputs constitutes a valid versus conflicting slot. It provides neither, leaving the agent to guess the result semantics of a constraint-checking tool.

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 six minute-valued parameters is already documented by the schema, which sets the baseline at 3. The description only groups them conceptually (shower time, assistance, room release) and adds no interpretation of units, ordering constraints, or how gemeinsam_min relates to the help window.

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 three resources it reconciles (Duschzeit, geplante Unterstützung, Raumfreigabe) and the constraint (ein belegtes Zeitfenster), so the domain is identifiable. However, the verb 'abstimmen'/'Align' is abstract: it never says whether the tool validates feasibility, computes a schedule, or checks consistency, and nothing distinguishes it from near-siblings like badezimmer_gemeinsame_nutzung_drei_mindestslots.

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 versus an alternative, no prerequisite, and no exclusion. The agent must infer from the parameter names alone that this is a planning/consistency check for an assisted shower slot.

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