Skip to main content
Glama

getecoback-climate-weather

miele_g7673_programmdauer_erste_auswahl_kaltwasserbasis

Read-only

Eine anfängliche Zeitangabe bei erstmaliger Programmauswahl als dokumentierten Referenzwert erkennen — Separate the first cold-water average from a running countdown.

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": {
      "modell_und_anzeige_belegt": "<modell_und_anzeige_belegt>",
      "erste_programmauswahl": "<erste_programmauswahl>",
      "vor_start": "<vor_start>",
      "zeit_gelesen": "<zeit_gelesen>",
      "dauer_min": "<dauer_min>"
    },
    "name": "miele_g7673_programmdauer_erste_auswahl_kaltwasserbasis"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_minYesGelesene Dauer. Wenn nichts gelesen wurde, 0 eingeben.
vor_startYesDie Ablesung war vor dem Start.
zeit_gelesenYesDer Minutenwert wurde für diese Auswahl tatsächlich gelesen.
erste_programmauswahlYesDie erste Auswahl dieses Programms ist tatsächlich bestätigt.
modell_und_anzeige_belegtYesGenaues Modell G 7673 SCVi AutoDos E und Zeitfeld identifiziert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety and scope are covered and the bar is lower. The description adds the meaningful distinction that the value captured must be the initial selection reading, not a countdown in progress — useful behavioral framing. It still says nothing about what is produced or stored when a reading is recorded.

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 with no filler, and the key qualifier (first selection, not countdown) lands early. The redundant German/English restatement of the same idea costs some clarity, but nothing is padded.

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?

With five required parameters, no output schema and only read-only annotations, the definition covers what to capture but not what the caller gets back or what a recorded reference value is used for. Adequate to invoke correctly, thin on outcome.

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 the schema already explains every one of the five required fields, establishing the baseline of 3. The description adds interpretive context for why erste_programmauswahl and vor_start matter (separating first selection from a running countdown), but gives no field-level detail beyond that.

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 an action ("erkennen", i.e. recognize/record) and an object (an initial duration reading at first program selection), and the second clause sharpens it to distinguishing a first cold-water reference value from a running countdown. But it never plainly says this tool records a first-time program-duration reading, and the bilingual abstraction makes the actual operation harder to grasp than the name already does. It does not identify itself against any sibling.

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?

"Separate the first cold-water average from a running countdown" implicitly scopes usage to the first selection rather than a live countdown, which is real but indirect guidance. There is no explicit when-to-use/when-not statement and no named alternative for the running-countdown case, so an agent must infer the boundary.

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