Skip to main content
Glama

getecoback-climate-weather

wasserkocher_twk8613p_min_max_markierungen_ablesbar

Read-only

Prüft die lesbare MIN- und MAX-Markierung am konkreten Bosch-Wasserkocher und ob 1,5 Liter allein den Mindeststrich belegen — Check legible on-device fill-limit markings before using an exact kettle.

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>",
      "min_ablesbar": "<min_ablesbar>",
      "max_ablesbar": "<max_ablesbar>",
      "gekennzeichnete_position": "<gekennzeichnete_position>"
    },
    "name": "wasserkocher_twk8613p_min_max_markierungen_ablesbar"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_ablesbarYesMAX am konkreten Gerät eindeutig abgelesen.
min_ablesbarYesMIN am konkreten Gerät eindeutig abgelesen.
anleitung_zugeordnetYesDas Gerät ist als deutsches TWK8613P identifiziert und die angegebene TWK86-Anleitung über die E-Nummer zugeordnet.
gekennzeichnete_positionYesWelche Füllung würde tatsächlich beobachtet?

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. The description adds that this is an on-device legibility observation tied to one identified appliance, but it says nothing about how the observations are judged or what conclusion the enums produce.

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?

The German and English halves largely duplicate each other, with only 'before using an exact kettle' adding new information in the second half. The core purpose is front-loaded, but roughly half the text is redundant restatement.

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, four-parameter diagnostic check with no output schema and full schema coverage, the description is sufficient to call it correctly. It is thin only on how the enum observations combine into a verdict, which the schema partially implies.

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 four parameters and their enums are already documented in the schema. The description confirms the on-device, specific-appliance framing and the 1.5-litre/minimum-mark question, which lightly reinforces the intent behind min_ablesbar and gekennzeichnete_position but adds no syntax or decision detail.

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 verb (prueft / check) and a concrete resource (the legible MIN and MAX markings on the specific Bosch TWK8613P kettle), plus the exact sub-question about 1.5 litres and the minimum mark. It does not explicitly name a sibling tool to contrast with, so it lands at 4 rather than 5.

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?

The trailing clause 'before using an exact kettle' implies the timing of use, but there is no explicit when-not guidance and no named alternative among the many sibling marking tools (e.g. fensterplatte_markierungen_nach_abnahme, philips_buegelgeraet_tankangabe_vs_gemessene_max_marke). Usage is inferred rather than stated.

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