Skip to main content
Glama

getecoback-raumklima

wasserkocher_twk8613p_vor_siedepunkt_abschaltung_sollwert

Read-only

Klärt, warum der Bosch Wasserkocher vor dem Siedepunkt abschaltet, mit Abgleich der Temperaturstufe und des beobachteten Verlaufs — Check whether an early-looking stop belongs to a lower setting or needs manufacturer review.

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>",
      "wahl": "<wahl>",
      "ende": "<ende>",
      "sichtbarer_kalk": "<sichtbarer_kalk>"
    },
    "name": "wasserkocher_twk8613p_vor_siedepunkt_abschaltung_sollwert"
  }
}

Input Schema

NameRequiredDescriptionDefault
endeYesDirekt beobachtetes Ende.
wahlYesBeim gestoppten Lauf bestätigte Einstellung.
sichtbarer_kalkYesKalkablagerungen sind als eigene Beobachtung am kalten Gerät belegt.
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

A3.9/5.0
Behavior4/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 adds the key behavioral promise: the tool returns a diagnosis with an escalation path (lower setting vs. manufacturer review), not raw data. It does not say how inconclusive 'offen' inputs are handled or what the verdict text looks like.

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 compact clauses, front-loaded with the problem statement followed by the actionable check; nothing is padded. The German/English duplication costs a little space but is clearly intentional for bilingual routing.

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

Completeness4/5

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

For a read-only, closed-world diagnostic with four fully documented parameters and no output schema, the description covers purpose, inputs to compare, and the two possible conclusions. The only gap is behavior on inconclusive evidence, which the 'offen' enum values hint at but the description never explains.

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% with self-explanatory enum and boolean descriptions, so the schema already carries parameter meaning. The description adds only the conceptual linkage between the confirmed setting and the observed run; it gives no guidance on when to submit 'offen' values for each field.

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?

States a specific diagnostic verb ('Klärt, warum ... abschaltet') tied to a concrete resource (the Bosch kettle stopping before boiling) and names the comparison basis (temperature setting vs. observed run). An agent can distinguish it from pure settings or display tools such as wasserkocher_wahlstufe_abgleichen, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second clause gives a clear decision context: use it when a stop looks early, to decide whether it is just a lower setting or warrants manufacturer review. It lacks an explicit 'do not use this when...' or a named alternative for the closed-world cases already covered by the enum values.

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