Skip to main content
Glama

getecoback-raumklima

spuelmaschine_tassenbestand_vor_servieren

Read-only

Vor einer Mahlzeit verfügbares Geschirr mit einer laufenden Ladung anhand der beobachteten Zeitreserve planen — Determine likely clean place settings available from existing stock and the current wash.

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": {
      "benoetigte_tassen": "<benoetigte_tassen>",
      "bereits_sauber": "<bereits_sauber>",
      "im_lauf": "<im_lauf>",
      "restlauf_min": "<restlauf_min>",
      "ausraeumen_min": "<ausraeumen_min>",
      "bis_servieren_min": "<bis_servieren_min>"
    },
    "name": "spuelmaschine_tassenbestand_vor_servieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
im_laufYesWeitere Tassen im bereits laufenden Programm.
restlauf_minYesAbgelesene oder selbst beobachtete Restlaufzeit.
ausraeumen_minYesEigene eingeplante Zeit vom Laufende bis zur Verfügbarkeit.
bereits_sauberYesAktuell verfügbare saubere Tassen.
benoetigte_tassenYesFür den Termin benötigte Tassen.
bis_servieren_minYesVerbleibende Zeit bis zum Bedarf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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. The description adds genuine behavioral context by framing the result as "likely" — a planning estimate derived from observed time reserves rather than a measured fact — but says nothing about how uncertainty is expressed or what the response contains.

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?

The core intent is front-loaded in the first clause, and the sentence is free of filler. The main inefficiency is that the German and English halves restate the same content, which is redundant for any reader who understands one of them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All six required parameters are fully specified in the schema and the description supplies the interpretive frame (stock + running wash + time reserve) needed to use them together. With no output schema, one could wish for a hint about the return form (count vs. verdict), but the phrase "likely clean place settings available" covers the essential outcome for a read-only planning 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 all six parameters are already documented with units and bounds. The description adds only a light conceptual grouping — "existing stock and the current wash" and "observed time reserve" — which maps parameters into roles but gives no formula, ordering, or edge-case meaning (e.g., restlauf exceeding bis_servieren). Baseline 3 applies.

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 computation: determine likely clean place settings available from (a) existing clean stock, (b) the running wash, and (c) the observed time reserve. That is a concrete verb+resource rather than a restatement of the name. It does not explicitly contrast itself with near siblings such as spuelmaschine_teller_tassen_getrennte_engpaesse, so it stops short of a 5.

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?

"Vor einer Mahlzeit" supplies a clear situational trigger — plan before a meal when a wash is still running — which implies when the tool is appropriate. However, it names no alternative tool and no exclusion condition (e.g., what to do when nothing is in the wash), so the guidance remains implied rather than explicit.

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