Skip to main content
Glama

getecoback-raumklima

wasserkocher_twk8613p_abheben_basis_kochen_neustart

Read-only

Klärt beim TWK8613P, ob er nach dem Abheben vom Sockel automatisch weiter heizt und die Einstellungen behält — Determine how a documented lift interrupts a kettle heating run.

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": {
      "anleitung_zugeordnet": "<anleitung_zugeordnet>",
      "vorgang": "<vorgang>"
    },
    "name": "wasserkocher_twk8613p_abheben_basis_kochen_neustart"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorgangYesTatsächlicher Vorgang während des Heizens.
anleitung_zugeordnetYesDas Gerät ist als deutsches TWK8613P identifiziert und die angegebene TWK86-Anleitung über die E-Nummer zugeordnet.

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 only needs to add context. It contributes that the answer depends on a 'documented' lift, hinting at the manual-assignment prerequisite, but it does not state what happens when anleitung_zugeordnet is false or what form the determination takes.

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, front-loaded clauses with the device and scenario stated first and no filler. The German and English halves are near-duplicates and the English version drops 'die Einstellungen behält', which is a minor redundancy/inconsistency rather than bloat.

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?

The input side is fully covered by a rich enum-plus-boolean schema, so the agent can call it correctly. However, there is no output schema and the description never indicates what a 'determination' returns (e.g., a verdict with conditions), which is the main missing piece for a query-type tool.

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 both parameters are already documented and the baseline is 3. The description's mention of lifting off the base and retaining settings loosely echoes the 'abgehoben_und_zurueckgestellt' enum value and the manual-assignment flag, but adds no new syntax or interpretation beyond the schema.

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 concrete scenario (TWK8613P lifted from its base during heating) and the two facts it resolves: whether heating resumes automatically and whether settings are retained. It is clearly narrower than neighbours like keep_warm_vor_heizende_aktivieren or temperatur_blinkt_leuchtet, though it never says explicitly that the tool returns a determination/rule answer rather than performing an action.

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 context is implied by 'beim Abheben vom Sockel' and 'documented lift', so an agent can infer the situation that calls for it. There are no explicit when-not conditions and no named alternative tools among the many similarly granular kettle siblings, leaving routing to inference.

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