Skip to main content
Glama

getecoback-climate-weather

miele_g7673_spuelanzeige_phase_eco_feedback

Read-only

Eine beobachtete Anzeige des Miele G 7673 SCVi AutoDos E dem richtigen Zustand zuordnen — Identify forecast bars, completed-run actuals, totals or remaining time.

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": {
      "g7673_de_belegt": "<g7673_de_belegt>",
      "anzeige": "<anzeige>",
      "belegphase": "<belegphase>"
    },
    "name": "miele_g7673_spuelanzeige_phase_eco_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzeigeYesTatsächlich gelesene Anzeigeart.
belegphaseYesIn der Anzeige dokumentierter Abschnitt.
g7673_de_belegtYesG 7673 SCVi AutoDos E und Anleitung G7673de-002 am konkreten Gerät belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the operation is an assignment of an observation to a state, reinforcing a non-mutating classification, but says nothing about error behavior, confidence, or what an ambiguous/unreadable result yields.

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 the resource and verb front-loaded, then a short enumeration of the target categories. The German/English duplication costs a little space but earns it as a bilingual aid.

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 three-parameter classification tool with full schema coverage and no output schema, the description is sufficient to call it correctly. It could note the unreadable/missing-evidence cases, but nothing critical is missing.

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%, so the baseline is 3. The description's English gloss translates four of the enum values (prognosebalken, verbrauch_abgelaufener_lauf, gesamtverbrauch, restzeit), which helps cross-language interpretation but is redundant with the schema and omits 'nicht_lesbar', 'belegphase', and 'g7673_de_belegt'.

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 pairs a specific verb (zuordnen / identify) with a specific resource (an observed display reading of the Miele G 7673) and enumerates the candidate categories: forecast bars, completed-run actuals, totals, remaining time. It is recognizable as a classification tool, though the bilingual phrasing and the dense naming make it a bit harder to parse at a glance.

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: you have a reading from the display and want to assign it to the correct state. There is no explicit 'use this instead of' routing, no prerequisites, and no statement about what to do when a reading is unreadable (the 'nicht_lesbar' enum exists in the schema but is never surfaced here).

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