Skip to main content
Glama

getecoback-raumklima

heizstart_vorlauf_planen

Read-only

Raumheizung anhand des beobachteten Wiederaufheizens vor der Nutzung starten — Plan morning heating lead time from measured recovery.

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": {
      "ready_hour": "<ready_hour>",
      "ready_minute": "<ready_minute>",
      "recovery_minutes": "<recovery_minutes>",
      "buffer_minutes": "<buffer_minutes>"
    },
    "name": "heizstart_vorlauf_planen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ready_hourYesGewünschte Uhrzeit auf der 24-Stunden-Uhr, ganze Stunde.
ready_minuteYesGewünschte Minute der Stunde, ganzzahlig.
buffer_minutesYesZusätzlicher Zeitpuffer in Minuten, ganzzahlig.
recovery_minutesYesGemessene Dauer bis zum gewünschten Raumkomfort in Minuten, ganzzahlig.

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 safety profile is covered and the agent knows this is a harmless computation. The description adds the useful framing that the computation is driven by *measured* recovery and a buffer, but it does not say what the tool actually returns (a start time or backwards-derived schedule), which matters because there is no output schema. Credit for the measurement-based framing, but the result shape is left implicit.

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 content is very short and front-loaded, which is good, but the German sentence and its English paraphrase duplicate the same information rather than complementing each other. For a bilingual audience this is defensible, yet half the text is repetition and no space is used for the missing output explanation.

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 four-required-parameter, closed-world computation tool with no output schema, the definition covers the inputs and the intent but omits what the caller gets back (e.g., a suggested heating start time) and how buffer interacts with recovery. It is adequate to invoke the tool but not complete enough to predict or use its result without trial.

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% and each of the four parameters is documented in-place (hour, minute, buffer, recovery), so the schema carries the detail. The description adds the semantic link that recovery_minutes is an *observed/measured* quantity rather than an assumed figure, which is genuinely useful interpretation, but it adds nothing about buffer or the ready-time pair beyond the schema. 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 specific action and object: it plans the start time of room heating based on measured reheating duration, so an agent can tell it computes a lead-time plan rather than measuring or reporting. The German/English pairing states the same purpose consistently. It does not distinguish itself explicitly from other planning siblings such as geraetetakt_aus_messung, but the resource (heating start time) is concrete enough to stand 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?

"vor der Nutzung" / "morning heating" implies the use case (planning a warm room before occupancy) but there is no explicit guidance on when to choose this over an alternative, nor any prerequisites or exclusions. With only contextual sibling names and no routing sentence, the agent must infer selection criteria.

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