Skip to main content
Glama

getecoback-raumklima

heizdecke_abschaltautomatik_einzelnutzung

Read-only

Die dokumentierte einmalige Abschaltautomatik in einem bereits zulässigen, beaufsichtigten Nutzungsabschnitt zeitlich berücksichtigen. — Account for documented auto-off within one already permitted, attended use.

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": {
      "gewuenscht_min": "<gewuenscht_min>",
      "dokumentiert_abschalt_min": "<dokumentiert_abschalt_min>",
      "nutzung_bestaetigt": "<nutzung_bestaetigt>"
    },
    "name": "heizdecke_abschaltautomatik_einzelnutzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gewuenscht_minYesGeplante beaufsichtigte Nutzungszeit in Minuten.
nutzung_bestaetigtYesAnleitung bestätigt diese konkrete Nutzungsart, Aufsicht, Stufe und Abschaltautomatik.
dokumentiert_abschalt_minYesAbschaltminuten ab Betriebsstart laut Anleitung genau dieses Modells und dieser Stufe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 contributes a genuine behavioral constraint beyond that — the use segment must already be permitted and attended, and the auto-off must be documented — but it never states what the call yields or what happens when dokumentiert_abschalt_min exceeds gewuenscht_min.

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?

A single short sentence, so nothing is padded, but the German and English renderings are exact duplicates and the English adds no information the German lacks. The one available sentence is spent on a vague verb rather than on the computation, so brevity here costs clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a three-required-parameter computation with no output schema, so the description must explain what the inputs produce. It never says whether the tool compares desired minutes against documented auto-off minutes, returns remaining minutes, or merely checks preconditions, leaving the agent unable to predict 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 all three parameters (desired minutes, documented auto-off minutes, confirmation flag) are already fully explained in the schema. The description adds no syntax, units, or interaction rules beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific subject (documented single-use auto-off) and a scope (one already permitted, attended use segment), but the operative verb 'berücksichtigen / account for' does not say what the tool actually does — validate, subtract, cap, or report the auto-off minutes. It also does not distinguish it from the sibling heizdecke_saison_vorlauf_abschaltcheck.

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?

No when-to-use or when-not-to-use guidance and no named alternative. The phrase 'in einem bereits zulässigen, beaufsichtigten Nutzungsabschnitt' is a precondition on the input, not routing guidance, so an agent must guess whether this tool or the sibling saison/vorlauf check applies.

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