Skip to main content
Glama

getecoback-climate-weather

raumversuch_erholungspausen_planen

Read-only

Wiederholte Lüftungsversuche mit Erholungspausen in ein echtes Zeitbudget einpassen — Schedule room trials with time to restore documented starting conditions.

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": {
      "verfuegbar_min": "<verfuegbar_min>",
      "lauf_min": "<lauf_min>",
      "rueckkehr_min": "<rueckkehr_min>",
      "ziel_laeufe": "<ziel_laeufe>"
    },
    "name": "raumversuch_erholungspausen_planen"
  }
}

Input Schema

NameRequiredDescriptionDefault
lauf_minYesVollständige Dauer eines Durchgangs einschließlich Messung, in Minuten.
ziel_laeufeYesGeplante Anzahl vollständiger Durchgänge.
rueckkehr_minYesEingeplante Pause vor jedem weiteren Lauf, um den Ausgangszustand erneut zu prüfen.
verfuegbar_minYesDauer des geplanten Messfensters, in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 closed-world computation. The description adds the substantive behavioral idea that each pause exists to restore documented starting conditions before the next run. It does not say what happens when the requested runs cannot fit the budget (error, truncation, or reduced count), which is the key behavioral question for a planning tool, and there is no output schema to compensate.

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

Conciseness3/5

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

The definition is short and front-loaded, but it says the same thing twice in German and English, so roughly half the text is redundant for any given reader. No structural waste beyond that duplication.

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?

Four required numeric parameters with full schema coverage and a read-only annotation profile make this a low-risk tool, so the bar is moderate. Still, with no output schema, the description never indicates what a caller receives back (e.g. a schedule of run start times or a feasibility verdict), which leaves a real gap for a planning 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 description coverage is 100% and all four parameters are documented in the schema, so the baseline is 3. The description reinforces the meaning of verfuegbar_min ('Zeitbudget') and rueckkehr_min ('restore documented starting conditions') but adds no units, ordering, or edge-case semantics beyond what the schema already states.

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 specific action and object: fitting repeated room/ventilation trials with recovery pauses into a time budget, i.e. scheduling trial runs. It does not distinguish this from the similarly named planning siblings (heizstart_vorlauf_planen, saugwischer_tankstopps_planen, stromversuch_wiederholungen_planen), so an agent must infer the domain difference from the tool name alone.

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: 'in ein echtes Zeitbudget einpassen' suggests this is the tool for when a fixed measurement window constrains how many trials fit. There is no explicit statement of when to prefer this over the other *_planen siblings and no exclusions or prerequisites.

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