Skip to main content
Glama

getecoback-raumklima

klimafenster_absprache_entfernung_wiedereinbau

Read-only

Fensterreinigung und anschließende Klimanutzung bei zwei fest eingeplanten Bedienpersonen koordinieren — Place a documented window-insert removal and restoration around cleaning.

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": {
      "reinigung_fertig_min": "<reinigung_fertig_min>",
      "wiedereinbau_person_ab_min": "<wiedereinbau_person_ab_min>",
      "wiedereinbau_pruefung_min": "<wiedereinbau_pruefung_min>",
      "klima_gebucht_ab_min": "<klima_gebucht_ab_min>",
      "verfahren_bestaetigt": "<verfahren_bestaetigt>"
    },
    "name": "klimafenster_absprache_entfernung_wiedereinbau"
  }
}

Input Schema

NameRequiredDescriptionDefault
klima_gebucht_ab_minYesGewünschter Beginn der nächsten Nutzung.
reinigung_fertig_minYesFrühestes Ende der Reinigung nach bereits bestätigter Abnahme auf der gemeinsamen Zeitachse.
verfahren_bestaetigtYesEignung, Abnahme und Wiedereinbau sind für diese Fensterlösung geklärt.
wiedereinbau_pruefung_minYesGemessene Minuten für vorgesehenen Wiedereinbau und Kontrolle.
wiedereinbau_person_ab_minYesPerson für den Wiedereinbau verfügbar ab dieser Minute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety is covered. The description adds the meaningful constraint that exactly two operators are assumed and that the removal/restoration is 'documented', but it says nothing about what happens when the inputs make the schedule infeasible or when verfahren_bestaetigt is false.

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?

Two short sentences with the domain context first, and the English clause usefully clarifies the German. The bilingual restatement is mildly redundant but not wasteful enough to hurt comprehension.

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-required-parameter coordination computation with no output schema, the description should say what result comes back (a feasible time window? a conflict flag?). That core outcome is missing, though the annotations at least establish that this is a safe read-only operation.

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 every parameter already carries a German explanation. The description adds no timing semantics (units, whether values are on a shared minute axis, how cleaning end interacts with reinstall availability) beyond what the schema provides; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the domain (window cleaning plus subsequent climate use) and the action ('koordinieren' / 'place ... around cleaning'), but what the tool actually produces — a schedule, a feasibility check, a placement plan — is never stated. It does not differentiate itself from the many sibling klimafenster tools that also deal with timing sequences.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no named alternative. 'two fixed scheduled operators' hints at a prerequisite context, but the agent is left to infer that this tool is for planning removal/restoration windows rather than for verifying an existing plan or comparing kits.

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