Skip to main content
Glama

getecoback-raumklima

wohnklima_geraetewechsel_rueckgabefrist_testfenster

Read-only

Vor einem bereits bekannten Abgabetermin zwei eigene Raumproben und Rückbau unterbringen — Fit two tests and pack-up before a known hand-back time.

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": {
      "jetzt": "<jetzt>",
      "rueckgabe": "<rueckgabe>",
      "a_min": "<a_min>",
      "b_min": "<b_min>",
      "wechsel_min": "<wechsel_min>",
      "rueckbau_min": "<rueckbau_min>",
      "aufbauten_geprueft": "<aufbauten_geprueft>"
    },
    "name": "wohnklima_geraetewechsel_rueckgabefrist_testfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_minYesDauer der vereinbarten Probe in A.
b_minYesDauer der vereinbarten Probe in B.
jetztYesZeitpunkt, ab dem das geliehene Gerät verfügbar ist.
rueckgabeYesVerbindlicher Übergabezeitpunkt am selben Tag.
wechsel_minYesBeobachtete Zeit für Umstellen und zugelassenen Aufbau.
rueckbau_minYesZeit für Abbau, Rücktransport und Verpackung laut eigener Planung.
aufbauten_geprueftYesBeide Aufbauten und der zulässige Transport am genauen Gerät geprüft?

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 purely computational, side-effect-free call. The description adds that the computation is anchored to a fixed return time and must absorb setup/transfer effort, but it never states what the tool actually produces (feasible window, boolean, or slack), which is the key behavioral fact for a checker of this kind.

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?

A single bilingual sentence with the time constraint ('before a known hand-back time') front-loaded and no filler. The German/English duplication adds length without new information, which keeps it from a 5.

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 seven-required-parameter computation with no output schema, the description explains the inputs' purpose but leaves the result shape entirely undefined. An agent can tell what to feed in but not what it will get back or how a failed fit is signalled, which is a real gap for a decision-support tool.

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 coverage is 100%, so every one of the seven parameters is already documented in the schema. The description reinforces that the two probe durations are 'own room tests' and that the return duration is a pack-up, but adds nothing about 'jetzt', 'wechsel_min', or how 'aufbauten_geprueft' gates the calculation. 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 names a concrete scheduling task: place two of your own room tests plus the pack-up ('Rückbau') before a fixed hand-back time. That is a specific verb-and-resource statement an agent can match to a scheduling-feasibility need. It does not name or differentiate itself from the scheduling sibling 'geraetewechsel_rechnen', which is the main missing element.

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?

Usage is only implied: you would call this when a return deadline is already known and two test durations must be accommodated. There is no explicit when-not condition, no mention of the precondition implied by 'aufbauten_geprueft', and no routing to alternative tools if the deadline is not fixed.

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