Skip to main content
Glama

getecoback-climate-weather

miele_g7673_automatisch_aus_dokumentierter_bezug

Read-only

Den dokumentierten automatischen Abschaltbezug von Ausschalten und Fehlern im beobachteten Ablauf trennen — Scope the ten-minute automatic-off behavior without asserting that it happened.

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": {
      "genauer_handbuchbezug": "<genauer_handbuchbezug>",
      "laufstatus": "<laufstatus>",
      "anzeigefehler": "<anzeigefehler>",
      "letzter_bezug": "<letzter_bezug>",
      "ausschaltbeobachtung": "<ausschaltbeobachtung>"
    },
    "name": "miele_g7673_automatisch_aus_dokumentierter_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
laufstatusYesBelegter Programmzustand zur fraglichen Zeit.
anzeigefehlerYesBelegter Fehlerzustand zur fraglichen Zeit.
letzter_bezugYesLetztes belegtes Bezugsereignis laut Notiz.
ausschaltbeobachtungYesAusschalten wurde separat am Gerät beobachtet.
genauer_handbuchbezugYesGenaues G 7673 SCVi AutoDos E und G7673de-002 bestätigt?

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 the meaningful epistemic caveat that the tool scopes the behavior 'without asserting that it happened', which prevents the agent from treating a result as confirmation. It says nothing about what the result contains or how conflicting inputs (e.g. laufstatus='laufend' with ausschaltbeobachtung=true) are handled.

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 short clauses: the German states the separation from Ausschalten and Fehlern, the English states the ten-minute scoping and the no-assertion constraint. The bilingual split is complementary rather than duplicated, and the key constraint sits at the end where it is easy to miss but the whole text is only one sentence long.

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 five-required-parameter, no-output-schema tool, the description never indicates what the invocation produces or how the inputs are combined into a documented reference. With annotations covering safety and the schema covering each field, this is adequate but leaves the agent guessing about the return value of an otherwise purely informational tool.

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% and all five required parameters carry their own descriptions and enums, so the schema does the heavy lifting. The description adds no parameter-level meaning — it never mentions Handbuchbezug, Laufstatus, Anzeigefehler, letzter Bezug, or the observation flag. Baseline 3 applies.

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 operation — separating the documented automatic-off reference from actual shutdown/error events in the observed sequence — and adds the explicit scope 'ten-minute automatic-off behavior'. That is a specific verb-plus-resource, not a restatement of the opaque tool name. It does not, however, name or contrast a sibling tool, leaving differentiation to the conceptual wording alone.

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 only implied: the tool is for scoping the ten-minute auto-off reference without asserting that it occurred, which suggests when it applies. No explicit when-to-use condition, prerequisite, or named alternative (e.g. an evidence-producing sibling) is given, so the agent must infer selection.

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