Skip to main content
Glama

getecoback-climate-weather

waesche_arbeitsfenster_umhaengen_abnehmen

Read-only

Einen flexiblen Umbau des Wäscheständers um einen festen Abholtermin herum einplanen — Place a manual rerack step around a fixed collection appointment.

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": {
      "beginn": "<beginn>",
      "ende": "<ende>",
      "abholen_ab": "<abholen_ab>",
      "abholen_dauer": "<abholen_dauer>",
      "umhaengen_ab": "<umhaengen_ab>",
      "umhaengen_dauer": "<umhaengen_dauer>"
    },
    "name": "waesche_arbeitsfenster_umhaengen_abnehmen"
  }
}

Input Schema

NameRequiredDescriptionDefault
endeYesEnde der verfügbaren Zeit.
beginnYesBeginn der verfügbaren Zeit, Minuten seit Mitternacht.
abholen_abYesFester Beginn der Abholung.
umhaengen_abYesFrühester Beginn für das Umhängen.
abholen_dauerYesFür die Abholung reservierte Minuten.
umhaengen_dauerYesZusammenhängende Dauer für das Umhängen.

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 safe, closed-world planning operation. The description adds the key scenario of a fixed collection appointment but does not explain the returned schedule, feasibility handling, or any behavioral limits beyond what the annotations provide.

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 a single, front-loaded sentence with no unnecessary explanation. The bilingual German/English rendering is slightly redundant but still compact and easy to parse.

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 tool is a six-parameter scheduling calculation with no output schema, and the description does not state what the planning result looks like or how infeasible cases are handled. The fully documented parameters and read-only annotation cover the invocation side, but the return-value context is left 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%, and each of the six time-window parameters is already documented in German within the schema. The description does not add syntax, constraints, or interpretation beyond the schema, so the baseline 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 states a specific verb and resource: planning ('einplanen') a flexible rerack ('Umbau des Wäscheständers') around a fixed collection appointment. This is clear enough for an agent to understand the operation without opening the schema, though it does not explicitly name or contrast a sibling tool.

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 'um einen festen Abholtermin herum' implies the usage context: schedule a rerack step when a fixed pickup appointment constrains the window. However, there is no explicit when-to-use statement, no exclusions, and no named alternative for cases without a fixed appointment.

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