Skip to main content
Glama

getecoback-climate-weather

haushalt_flexible_laufpause_mindestabschnitte

Read-only

Eine bestätigte pausierbare Aufgabe auf zwei freie Nutzungsblöcke mit je eigener Wiederanlaufzeit verteilen — Check piecewise progress after deducting restart work in two shared slots.

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": {
      "freier_block_a_min": "<freier_block_a_min>",
      "freier_block_b_min": "<freier_block_b_min>",
      "jeweilige_vorbereitung_min": "<jeweilige_vorbereitung_min>",
      "netto_noetig_min": "<netto_noetig_min>",
      "pause_zulaessig": "<pause_zulaessig>"
    },
    "name": "haushalt_flexible_laufpause_mindestabschnitte"
  }
}

Input Schema

NameRequiredDescriptionDefault
pause_zulaessigYesDie Aufgabe ist laut Anleitung im geplanten Zustand unterbrechbar und fortsetzbar.
netto_noetig_minYesReine Bearbeitungszeit, ohne Vorbereitungen.
freier_block_a_minYesErster bestätigter freier Block für dasselbe geeignete Gerät.
freier_block_b_minYesZweiter bestätigter freier Block auf derselben Zeitachse.
jeweilige_vorbereitung_minYesIn jedem benutzten Block notwendiger gemessener Zeitbedarf ohne Fortschritt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety and side-effect profile are covered and the description need not restate them. The description adds that restart/preparation overhead is deducted before progress is computed, which is genuine behavioral context. What it omits is the shape of the result — whether it returns feasibility, per-block allocation, leftover time, or a failure indicator — which matters since there is 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?

It is a single sentence, so it is compact, but it duplicates the same content in German and English rather than letting one version carry the load, and the dense compound jargon ('Wiederanlaufzeit', 'Nutzungsblöcke') makes it hard to parse. The front-loaded German clause is the informative part; the English gloss adds little.

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 five required inputs are fully specified in the schema, so an agent can construct a call. But this is a computation tool with no output schema, so the description is the only place that could explain what comes back, and 'Check piecewise progress' is too vague to tell an agent how to interpret or use the result.

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 every parameter is already documented in the schema (free block A/B minutes, per-block preparation minutes, net required minutes, pausability flag). The description only echoes the two-block structure and the 'restart work' notion, adding no syntax, units, or constraint detail beyond the schema. Baseline 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 German half names a specific operation (distribute a confirmed pausable task across two free usage blocks, each with its own restart time), which is more than a restatement of the name. However, the English half ('Check piecewise progress after deducting restart work in two shared slots') is vague and does not clearly state whether the tool schedules, validates feasibility, or returns a progress check. No sibling is named to distinguish this two-slot variant from e.g. the three-slot '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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. The only implicit cue is 'bestätigte pausierbare Aufgabe', which hints at a precondition (task confirmed pausable) but never states it as a selection rule or names what to call instead for non-pausable or single-block cases.

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