Skip to main content
Glama

getecoback-raumklima

wasserkocher_twk8613p_wasser_milch_instant_einfuellen

Read-only

Prüft, ob frisches kaltes Wasser, Milch oder fertiges Instantgetränk laut Bosch in den Kessel gehört — Check the manufacturer’s kettle liquid scope against the household use case.

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>",
      "fluessigkeit": "<fluessigkeit>"
    },
    "name": "wasserkocher_twk8613p_wasser_milch_instant_einfuellen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fluessigkeitYesGeplanter Kanneninhalt.
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, and the description is consistent with a non-mutating verification. It adds the useful framing that the answer is scoped to Bosch's manufacturer specification versus the household's intended use. However, with no output schema it never says what the verdict looks like or how a 'not permitted' outcome is surfaced.

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?

A single, front-loaded sentence with no padding, and the German/English pairing is a deliberate bilingual convenience rather than filler. The two halves are paraphrases, so there is a small amount of duplication, but nothing that obscures the core statement.

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 two-parameter read-only check with no output schema, the description should say what kind of answer the agent will get and how to interpret a negative result; it does neither. The prerequisite condition (device identified as the German TWK8613P with the TWK86 manual assigned) is left entirely to the schema, which does cover it.

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 in the schema, making 3 the baseline. The description's mention of water, milk, and instant drink maps onto part of the enum, but it says nothing about the variant values ('kohlensaeurewasser', 'offen') or about the meaning of the 'anleitung_zugeordnet' prerequisite.

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 verb ('Prüft, ob ... gehört') and a specific resource scope: whether fresh cold water, milk, or a ready-made instant drink is permitted in the Bosch kettle. That is distinguishable from siblings, which cover descaling, base placement, keep-warm, and temperature faults. It loses a point because the tool name says 'einfuellen' (fill) while the description says 'check whether it belongs', leaving mild doubt about whether this performs an action or a verification.

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 is implied rather than stated: the check is framed 'against the household use case', suggesting it is called when the user plans to put a given liquid in the kettle. There is no explicit when-to-use, no when-not-to-use, no prerequisites, and no named alternative among the many siblings.

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