Skip to main content
Glama

getecoback-climate-weather

klima_herbst_trocknungsfenster_planen

Read-only

Den dokumentierten Trocknungslauf vor dem Transport in ein freies Herbst-Zeitfenster einplanen — Fit a documented end-of-season drying run before pick-up.

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": {
      "fenster_ab": "<fenster_ab>",
      "abholung_min": "<abholung_min>",
      "trocknung_min": "<trocknung_min>",
      "nachlauf_min": "<nachlauf_min>",
      "vorgabe_bekannt": "<vorgabe_bekannt>"
    },
    "name": "klima_herbst_trocknungsfenster_planen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_abYesBeginn des laut Anleitung nutzbaren Zeitfensters. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
abholung_minYesGeplanter Zeitpunkt des Transports oder Verpackens. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
nachlauf_minYesEigener Puffer für die anschließende Sichtkontrolle und übrigen Schritte. In Minuten.
trocknung_minYesUnunterbrochene Dauer laut Geräteanleitung. In Minuten.
vorgabe_bekanntYesSind Betriebsart und erforderliche Dauer für das genaue Modell belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety profile is covered. The description adds the constraint that the run must be 'dokumentiert', which mirrors the vorgabe_bekannt parameter, but it says nothing about what happens when no window fits, whether the call fails or reports infeasibility, or how the result is expressed.

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 front-loaded sentence that pairs the German original with an English rendering, with no filler. The bilingual duplication costs a little length but keeps the definition compact.

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 read-only with fully specified inputs, so the schema carries most of the burden. However, with no output schema the description should indicate whether the call returns a scheduled window or a feasibility failure — that gap matters for a planning tool whose whole point is fitting constraints.

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 is already documented with units and bounds; the baseline of 3 applies. The description only loosely gestures at 'freies Zeitfenster' and 'dokumentierter Trocknungslauf' and adds no 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 names a specific action (einplanen/schedule) and a specific resource (a documented drying run into a free autumn window before pick-up). An agent can grasp the operation without opening the schema, but nothing distinguishes it from near-siblings such as saros10r_filter_trocknungsfenster or heizstart_vorlauf_planen.

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?

The phrase 'vor dem Transport' implies a sequencing context, but there is no explicit statement of when this tool should be chosen over the many other klima_* planning tools, and no prerequisites or exclusions are given.

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