Skip to main content
Glama

getecoback-climate-weather

geraetelauf_aufsichtswechsel_zeitplan

Read-only

Eine Aufgabe mit getrennten Start- und Endhandgriffen gegen tatsächlich besetzte Zeitfenster prüfen — Find a feasible finish when different people handle launch and unload at known times.

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": {
      "lauf_min": "<lauf_min>",
      "a_bis_min": "<a_bis_min>",
      "b_von_min": "<b_von_min>",
      "b_bis_min": "<b_bis_min>",
      "warte_limit_min": "<warte_limit_min>",
      "betrieb_erlaubt": "<betrieb_erlaubt>"
    },
    "name": "geraetelauf_aufsichtswechsel_zeitplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
lauf_minYesBeobachtete Dauer des unbeeinflussten Programms in Minuten.
a_bis_minYesLetzter möglicher Start durch Person A, Minuten seit Beginn des Planungstages.
b_bis_minYesLetzte mögliche Entnahme durch Person B, Minuten seit Beginn des Planungstages.
b_von_minYesFrüheste mögliche Entnahme durch Person B, Minuten seit Beginn des Planungstages.
betrieb_erlaubtYesHersteller erlaubt die geplante Betriebsart und Haushaltsregeln sind geprüft?
warte_limit_minYesSelbst gewählte maximale Zeit von Ende bis 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 safety profile is covered. Beyond that the description only says it finds a feasible finish; it does not say what happens when no feasible finish exists, what the result looks like (a time vs. a boolean), or that the betrieb_erlaubt flag acts as a hard gate that can veto the whole schedule.

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, but the German sentence and the English sentence largely restate each other rather than front-loading complementary information. Half the text is redundancy in a bilingual pair, and the outcome the tool produces is never stated.

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?

With six required numeric/boolean parameters and no output schema, the description should at least characterize the returned result (earliest feasible finish? infeasibility signal?), which it does not. The read-only nature is covered by annotations, but the description also references 'actually occupied time windows' that have no corresponding parameter, leaving a conceptual mismatch.

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 German, which sets the baseline at 3. The description adds the conceptual mapping of 'launch handled by A' vs 'unload by B', which helps interpret a_bis_min versus b_von_min/b_bis_min, but it says nothing about warte_limit_min or the betrieb_erlaubt gate, so the added meaning is marginal.

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 names a specific operation (checking a task with separate start/end handlers and finding a feasible finish) with a concrete scope (launch handled by one person, unload by another). It is distinguishable as a feasibility/scheduling computation, though it never contrasts itself with the many sibling *_zeitplan tools.

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?

The description implies a scenario (different people handle launch and unload at known availability times) but gives no explicit when-to-use rule, no prerequisites, and no routing to alternatives such as the other two-machine or pause-scheduling siblings. An agent must infer selection from the scenario wording alone.

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