Skip to main content
Glama

getecoback-raumklima

spuelmaschine_zwischenlauf_abstellfolge

Read-only

Zwischen zwei geplanten Läufen Ausräumen und Nachladen mit der tatsächlich verfügbaren Person abstimmen. — Confirm separate unloading and loading availability between two dishwasher runs.

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": {
      "zuerst_fertig_min": "<zuerst_fertig_min>",
      "spaetestens_zweiter_start_min": "<spaetestens_zweiter_start_min>",
      "person_frei_ab_min": "<person_frei_ab_min>",
      "person_frei_bis_min": "<person_frei_bis_min>",
      "aus_und_einraeumen_min": "<aus_und_einraeumen_min>"
    },
    "name": "spuelmaschine_zwischenlauf_abstellfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuerst_fertig_minYesErster Lauf fertig auf der gemeinsamen Minutenachse.
person_frei_ab_minYesBeginn der im Übergang verfügbaren Bedienzeit.
person_frei_bis_minYesEnde derselben zusammenhängenden Bedienzeit.
aus_und_einraeumen_minYesGemessene Gesamtzeit für beide Arbeiten ohne laufendes Programm.
spaetestens_zweiter_start_minYesSpätester Start des nächsten Laufs auf derselben Achse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 agent knows this is a side-effect-free, closed-world computation; the description adds little beyond that. 'Confirm ... availability' weakly signals that a feasibility verdict is produced, but it never states what the answer looks like or how infeasibility (e.g. the person window not covering the required total time) is reported.

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?

Two short sentences, front-loaded with the situation and the action; nothing is padded with hedging or restated field lists. The English sentence largely duplicates the German one, which is defensible for a bilingual catalog but adds no new information.

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 five required numeric parameters and no output schema, the description should at minimum indicate what comes back and what makes the plan infeasible. It hints at a confirmation/verdict but leaves the return value and any failure condition unexplained, so it is adequate rather than complete for a scheduling-feasibility 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%, and each of the five numeric parameters is documented in the schema with its meaning on the shared minute axis, so the schema carries the load. The description only contributes the framing that the person window is understood as actually available staffing time and that both work steps are measured together; that is helpful context but not added semantics for individual arguments.

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 concrete operation on a concrete resource: reconcile unloading plus reloading with the actually available person between two planned dishwasher runs. The English gloss 'Confirm separate unloading and loading availability' makes the check-like nature clearer than the German 'abstimmen'. It does not, however, distinguish this from the many sibling spuelmaschine_* tools that also deal with capacity, timing or loading.

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?

The phrase 'between two planned runs' implies the scenario in which the tool applies, so usage is inferable. There is no explicit statement of when not to use it, no named alternative (e.g. a pure scheduling or capacity tool among the siblings), and no prerequisites about the shared minute axis the caller must supply.

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