Skip to main content
Glama

getecoback-raumklima

dampfreiniger_nachfuellpause_zwei_arbeitsinseln

Read-only

Bei einem dokumentierten Nachfüllstopp eine getrennte trockene Aufgabe in die beobachtete Wartezeit einpassen — Schedule a separate dry task during a documented refill wait.

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": {
      "warte_min": "<warte_min>",
      "bewegung_min": "<bewegung_min>",
      "aufgabe_min": "<aufgabe_min>",
      "unbeaufsichtigt_zulaessig": "<unbeaufsichtigt_zulaessig>"
    },
    "name": "dampfreiniger_nachfuellpause_zwei_arbeitsinseln"
  }
}

Input Schema

NameRequiredDescriptionDefault
warte_minYesBeobachtete gesamte Wartezeit nach Anleitung für das konkrete Gerät.
aufgabe_minYesBenötigte zusammenhängende Zeit für die separate trockene Aufgabe.
bewegung_minYesZeit zur trockenen Aufgabe und zurück.
unbeaufsichtigt_zulaessigYesIst der vorgeschriebene Gerätezustand während der eigenen Abwesenheit laut passender Anleitung zulässig?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already establish that this is a read-only, closed-world tool, and the description adds that the task must be separate and dry during a documented refill wait. However, it does not explain the calculation outcome, whether it returns a feasibility check or a schedule, or how the unattended-permission field affects behavior.

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 description is a single front-loaded sentence with the condition first and the task second, and it has no unnecessary filler. The bilingual duplication is slightly redundant but not harmful.

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?

The input schema fully documents all required parameters, and the annotations cover safety and scope. Because there is no output schema, the description should do more to explain what the tool returns or how the fit decision is expressed, but it provides enough context to call the tool correctly.

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 four parameters already have clear meanings in the input schema. The description does not add parameter-specific guidance, but with full schema coverage the baseline score of 3 is appropriate.

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 ('einpassen' / schedule) and a specific resource ('getrennte trockene Aufgabe') within a refill wait. It is understandable without opening the schema, though it does not explicitly explain the 'zwei Arbeitsinseln' framing or distinguish this from related scheduling siblings.

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?

It gives a clear trigger condition: use during a documented refill stop to fit a separate dry task into the observed wait. It does not state when not to use it, what alternative tool to choose for other task types, or any additional prerequisites beyond what the schema fields imply.

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