Skip to main content
Glama

getecoback-raumklima

spuelmaschine_eco_sperrzeit_budget

Read-only

Beobachtete Laufzeiten anhand einer nachfolgenden bewusst freigehaltenen Küchenzeit planen — Compare how far a measured dishwasher cycle would extend into a shared-room no-run interval.

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": {
      "start_min": "<start_min>",
      "eco_dauer_min": "<eco_dauer_min>",
      "alternative_dauer_min": "<alternative_dauer_min>",
      "sperre_beginnt_min": "<sperre_beginnt_min>",
      "sperre_endet_min": "<sperre_endet_min>"
    },
    "name": "spuelmaschine_eco_sperrzeit_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_minYesGeplanter Start als Minute ab demselben Planbeginn.
eco_dauer_minYesEigene beobachtete Dauer des gewählten Eco-Programms.
sperre_endet_minYesEnde des freigehaltenen Intervalls.
sperre_beginnt_minYesBeginn des freigehaltenen Intervalls.
alternative_dauer_minYesEigene beobachtete Dauer eines zugelassenen alternativen Programms.

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?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-domain operation. The description adds the behavioral idea of comparing runtime extension into a reserved interval, but it does not explain the calculation, assumptions, or result semantics.

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 definition is short and front-loaded toward the planning comparison. The German and English versions largely duplicate each other and the transition between them is slightly awkward, but there is little wasted content.

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?

For a five-parameter calculation tool with no output schema, the description does not state what the result represents, such as overlap minutes, an end time, or a boolean conflict. It is adequate given full schema coverage, but it leaves return semantics and assumptions implicit.

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 five parameters are already documented in the input schema. The description only alludes to measured durations and the reserved interval, adding no extra parameter meaning, units, or edge-case guidance beyond the schema.

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 states a specific planning/comparison action: checking how far a measured dishwasher cycle extends into a deliberately reserved kitchen no-run interval. It identifies the relevant resource concepts (measured runtimes and shared-room interval), but does not distinguish this tool from any named sibling alternative.

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 use context is implied: plan observed dishwasher runtimes against a later reserved interval. However, there is no explicit when-to-use versus when-not guidance and no alternative tool is named.

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