Skip to main content
Glama

getecoback-climate-weather

miele_g7673_einstellungen_wlan_ruecksetzbelege

Read-only

Bei vorhandener Rücksetznotiz die dokumentierten Einstellungen und den getrennten WLAN-Bereich auseinanderhalten — Determine retained evidence without initiating any reset.

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_handbuch_belegt": "<g7673_handbuch_belegt>",
      "werksbereich_belegt": "<werksbereich_belegt>",
      "wlan_vorhanden": "<wlan_vorhanden>",
      "wlan_belegt": "<wlan_belegt>"
    },
    "name": "miele_g7673_einstellungen_wlan_ruecksetzbelege"
  }
}

Input Schema

NameRequiredDescriptionDefault
wlan_belegtYesFür vorhandenen WLAN-Bereich liegt eine separate Bestätigung vor.
wlan_vorhandenYesIst ein entsprechender WLAN-Bereich laut Unterlagen vorhanden?
werksbereich_belegtYesEine separate Bestätigung zum Einstellungsbereich liegt vor.
g7673_handbuch_belegtYesGenaues Gerät und passende Anleitung 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; the description reinforces this with 'without initiating any reset', which is useful confirmation but largely duplicative. It does not disclose what the tool returns for the four evidence inputs, nor how conflicting evidence (e.g. wlan_vorhanden='unklar') is handled.

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 precondition is front-loaded, which is good, but the German clause is dense and abstract and the English half mostly restates it rather than extending it. The bilingual duplication costs length without adding new information.

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?

With annotations covering the safety profile, full schema coverage, and no output schema, the description supplies the two things structure cannot: the precondition and the explicit no-reset guarantee. What remains missing is any statement of the return value, which matters because there is no output schema to fall back on.

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 are already documented at the field level, establishing a baseline of 3. The description only loosely gestures at two of them ('dokumentierten Einstellungen', 'getrennten WLAN-Bereich') and adds no rule for how the four inputs combine into a determination.

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 the operation (distinguishing whether documented settings evidence and a separate WLAN-area confirmation exist) and explicitly states it does not perform a reset, which the opaque tool name alone would not convey. The German verb 'auseinanderhalten' is not a standard operation verb and only the English clause 'Determine retained evidence' makes the purpose fully legible.

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?

Includes a precondition ('Bei vorhandener Rücksetznotiz') which implies when the tool applies, and rules out the reset action itself. It never names an alternative sibling or states when *not* to call it, so the routing guidance is only implied.

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