Skip to main content
Glama

getecoback-raumklima

heissluft_folgelauf_vorheizen_konfiguration

Read-only

Einen gemessenen ersten und zweiten Vorheizabschnitt als Teil zweier dokumentiert zulässiger Folgeläufe einordnen. — Evaluate the extra heat-up occupation observed in a compatible follow-on cycle.

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_vorlauf_min": "<erster_vorlauf_min>",
      "zweiter_vorlauf_min": "<zweiter_vorlauf_min>",
      "wechsel_min": "<wechsel_min>",
      "gleiche_einstellung": "<gleiche_einstellung>"
    },
    "name": "heissluft_folgelauf_vorheizen_konfiguration"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechsel_minYesZusätzliche Zeit dazwischen beim zulässigen Folgelauf gegenüber zwei Einzelstarts.
erster_vorlauf_minYesProtokollierte Vorheizzeit bei einem üblichen Einzelstart.
gleiche_einstellungYesErfolgten die Durchgänge mit vergleichbarem Programm und gleichen Einstellungen laut Anleitung?
zweiter_vorlauf_minYesProtokollierte Vorheizzeit für dasselbe Programm im zulässigen Folgelauf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safe, closed-world read/compute operation and the description needn't repeat that. The description does add the domain constraint that the segments belong to two documented permissible follow-on cycles, but it never states what kind of result 'einordnen' produces (verdict, classification, numeric comparison) — a real gap given 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?

Very short and front-loaded: the core intent is in the first sentence. The German/English duplication is slightly redundant and the German construction is convoluted, but no sentence is padded or buried.

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 four-required-parameter evaluation tool with no output schema, yet the description never says what the evaluation returns or on what basis the segments are judged compatible beyond the boolean parameter. For a tool whose whole purpose is classification, the omission of the result semantics leaves the definition materially incomplete.

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%, and the parameter descriptions already explain erster/zweiter_vorlauf_min, wechsel_min and gleiche_einstellung in domain terms. The description adds no additional parameter meaning or expected value ranges, so the baseline 3 for a fully documented schema 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 operation ('Einen gemessenen ersten und zweiten Vorheizabschnitt ... einordnen' / 'Evaluate the extra heat-up occupation') on two measured resources, which is more than a tautology. However, the phrasing is opaque jargon and the bilingual restatement in English ('Evaluate the extra heat-up occupation observed in a compatible follow-on cycle') is vaguer than the German, leaving the agent unsure whether this classifies, validates, or computes something about the segments.

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?

There is no when-to-use / when-not-to-use guidance, no prerequisite stating that the segments must come from a documented permissible follow-on cycle before calling, and no route to any of the many sibling heat-up tools. The agent must infer applicability from the input parameters alone.

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