Skip to main content
Glama

getecoback-raumklima

klimageraet_fruehjahrsstart_ruhezeit

Read-only

Den ersten Start der mobilen Klimaanlage nach der modellbezogenen Ruhezeit planen — Schedule a portable AC restart after the documented settling period.

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": {
      "aufgestellt_min": "<aufgestellt_min>",
      "start_geplant_min": "<start_geplant_min>",
      "ruhezeit_min": "<ruhezeit_min>",
      "vorgabe_bekannt": "<vorgabe_bekannt>"
    },
    "name": "klimageraet_fruehjahrsstart_ruhezeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruhezeit_minYesRuhezeit aus der Anleitung für die konkrete Transportlage, bei fehlender Angabe 0 eintragen. In Minuten.
aufgestellt_minYesWann stand das Gerät am Zielort in der vorgeschriebenen Position? Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
vorgabe_bekanntYesLiegt eine eindeutige Modellvorgabe für diese Transportlage vor?
start_geplant_minYesGewünschte Startzeit. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 pure computation with no side effects, and the description correctly reads as planning rather than executing. Beyond that it adds only the scoping fact that the rest period is model-dependent; it does not say what the call produces (a computed earliest start, a verdict, an error) or how a missing specification is handled, which matters for a tool with 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?

Two short sentences with the core action front-loaded in the German clause and a parallel English restatement. The bilingual duplication adds a little redundancy but no wasted reasoning, and nothing essential is buried.

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 four parameters are fully documented in the schema and the annotations cover safety, so the definition is callable. What remains missing is the result: with no output schema and no description of the return value, an agent cannot tell whether it receives a timestamp, a boolean feasibility flag, or a warning when vorgabe_bekannt is false.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so per the baseline rule the schema carries the parameter burden. The description still adds real meaning by tying the run to a "modellbezogene Ruhezeit", which frames ruhezeit_min and vorgabe_bekannt as specification-driven rather than arbitrary numbers, linking the four parameters into one coherent computation.

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 ("den ersten Start ... planen" / "schedule a restart") and a specific object (portable AC after the model-specific settling period), which is enough for an agent to distinguish a first-start/rest-period computation from the measurement and check siblings. It stops short of stating explicitly how it differs from adjacent tools such as kondenswasser_check or the noise tools, so it is clear but not sharply differentiated.

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?

The phrase "nach der modellbezogenen Ruhezeit" implies the situation in which the tool applies (after transport/setup, once the documented rest period is known), but there is no explicit when-to-use instruction, no statement of what to do when no model spec exists, and no named alternative. Usage is inferable rather than prescribed.

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