Skip to main content
Glama

getecoback-raumklima

waesche_abholzeit_trommel

Read-only

Feuchte Wartezeit einer Ladung zwischen Programmende und geplanter Entnahme berechnen — Calculate how long finished wet laundry would wait before collection.

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_in_min": "<start_in_min>",
      "laufzeit_min": "<laufzeit_min>",
      "abholen_in_min": "<abholen_in_min>"
    },
    "name": "waesche_abholzeit_trommel"
  }
}

Input Schema

NameRequiredDescriptionDefault
laufzeit_minYesBeobachtete Laufzeit des Programms in Minuten.
start_in_minYesGeplanter Programmstart in Minuten ab jetzt.
abholen_in_minYesMögliche Entnahme in Minuten ab jetzt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The read-only nature is already covered by the annotations, so the description does not need to restate safety. It explains the computed quantity but adds no detail about edge cases, expected output shape, or how inputs affect the result.

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

Conciseness5/5

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

The definition is a single compact sentence with the core calculation front-loaded. The German and English phrasing are both short and there is no unnecessary wording.

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?

For a simple read-only calculation with three fully documented parameters, the description is nearly complete. It could mention the output more explicitly or clarify edge cases, but the schema and annotations cover the main gaps.

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 all three parameters are fully documented there. The description introduces the concepts of program end and collection time but does not add syntax, constraints, or interpretation 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 calculation: the waiting time between program end and planned collection for wet laundry. It is clear and actionable, but it does not explicitly differentiate itself from sibling laundry-planning 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?

The description implies the tool is used when scheduling laundry collection after a wash cycle. It does not state when not to use it or name any alternative sibling tool for related calculations.

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