Skip to main content
Glama

getecoback-climate-weather

mobilklima_zweiraum_folgeplan

Read-only

Ein vorhandenes Mobilgerät vor zwei aufeinanderfolgenden Raumterminen einplanen — Check when one portable unit can serve two rooms in a fixed sequence.

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": {
      "erster_termin_min": "<erster_termin_min>",
      "zweiter_termin_min": "<zweiter_termin_min>",
      "erste_phase_min": "<erste_phase_min>",
      "zweite_phase_min": "<zweite_phase_min>",
      "wechsel_min": "<wechsel_min>"
    },
    "name": "mobilklima_zweiraum_folgeplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechsel_minYesRealer Wechselaufwand inklusive der laut Anleitung nötigen Schritte. In Minuten.
erste_phase_minYesVor Ort gemessene Kühlzeit bis zum selbst gesetzten Ziel in Raum 1. In Minuten.
zweite_phase_minYesEntsprechende, separat gemessene Zeit in Raum 2. In Minuten.
erster_termin_minYesZeitpunkt, für den der erste Raum vorbereitet sein soll. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
zweiter_termin_minYesZeitpunkt für den zweiten Raum. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.

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 safety profile is covered and the description is consistent with it. Beyond that, 'Check when ... can serve' usefully signals a feasibility decision rather than a scheduling mutation, but nothing is said about what the verdict contains or how infeasibility is expressed — a real gap since there is no output schema.

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 with no filler, stating the constraint (existing unit, two consecutive appointments, fixed order) immediately. The German/English duplication is redundant but serves as a gloss rather than padding, so only a small deduction.

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?

All five required parameters are self-documenting and the read-only nature is declared, so an agent can call it correctly. Completeness falls short on the outcome side: with no output schema and no statement of what the feasibility check returns, the agent cannot anticipate the response shape or units of the result.

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 one of the five numeric parameters is already explained in the schema (minute-based units, ranges up to 2880 and 10080). The description only restates the two-appointment framing and adds no interpretation of the phases or the changeover offset beyond the schema. Baseline 3 applies.

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 uses a specific verb and resource ('Ein vorhandenes Mobilgerät ... einplanen' / 'Check when one portable unit can serve two rooms') and adds the decisive scope constraint: exactly two rooms in a fixed sequence. This is concrete enough to separate it from the many measurement/setup tools in the sibling list, although no sibling is named explicitly.

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 implied by the scenario: you invoke it when a single portable unit has to cover two room appointments back-to-back. There is no when-not guidance (e.g., what to do for parallel, overlapping, or more than two rooms) and no alternative named, so the agent must infer the boundary conditions.

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