Skip to main content
Glama

getecoback-raumklima

waesche_zwei_maschinen_zeitplan

Read-only

Mehrere gleiche Ladungen über getrennte Waschmaschine und Trockner zeitlich planen — Schedule repeated laundry batches through two separate appliances.

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": {
      "ladungen": "<ladungen>",
      "wasch_min": "<wasch_min>",
      "trocken_min": "<trocken_min>",
      "deadline_min": "<deadline_min>"
    },
    "name": "waesche_zwei_maschinen_zeitplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ladungenYesZahl gleichartiger, für beide Geräte geeigneter Ladungen.
wasch_minYesBelegungszeit der Waschmaschine je Ladung in Minuten.
trocken_minYesBelegungszeit des Trockners je Ladung in Minuten.
deadline_minYesVerfügbares Zeitfenster ab dem ersten Start in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish the safety profile (readOnlyHint=true, openWorldHint=false), so the burden is lighter, but the description adds almost no behavior beyond them. It does not say what the tool returns (a schedule of start times? a feasibility verdict?), nor what happens when the deadline cannot be met, which matters for a planning computation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no hedging or boilerplate, and the key constraint (two separate appliances, repeated identical batches) comes first. The German/English duplication is a minor redundancy but keeps it brief.

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 four required numeric parameters and no output schema, the definition should describe the returned plan and the failure mode when the window is too small; neither appears. The modeling assumptions (sequential machine occupancy, no overlap between washer and dryer, whether all batches must be identical) are left unstated, which is a real gap for a scheduling 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%, with each of the four required parameters documented, so the baseline of 3 applies. The description adds no extra meaning such as how deadline_min interacts with the two occupancy durations or whether wash and dry may overlap.

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 action (zeitlich planen / schedule) and a specific resource (repeated identical laundry batches run through a separate washer and dryer). An agent can tell this is a two-appliance batch-scheduling computation rather than, say, a cost or measurement tool. It stops short of naming a sibling tool or explicitly contrasting itself with the other waesche_* tools.

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?

Applicability is only implied through the wording 'über getrennte Waschmaschine und Trockner' and 'Mehrere gleiche Ladungen', i.e. it fits when several equal batches must be ordered across two machines. There is no explicit when-to-use, when-not-to-use, prerequisite, or named alternative among the many laundry siblings, so the agent must infer selection criteria.

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