Skip to main content
Glama

getecoback-climate-weather

bosch_wgb244a40_idos_45kg_basis_oder_istmenge

Read-only

Bosch WGB244A40 i-DOS Basisdosierung für 4,5 kg normal verschmutzte Wäsche mit Packung abgleichen — Distinguish the Bosch base setting from an actual cycle dose.

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": {
      "modellbeleg": "<modellbeleg>",
      "packungswert_bezug": "<packungswert_bezug>",
      "basis_anzeige_ml": "<basis_anzeige_ml>",
      "vergleich_packung_ml": "<vergleich_packung_ml>",
      "aktuelle_ladung_kg": "<aktuelle_ladung_kg>"
    },
    "name": "bosch_wgb244a40_idos_45kg_basis_oder_istmenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellbelegYesStehen WGB244A40 und der E-Nr.-Index am eigenen Gerät und ist dafür die deutsche Anleitung 9001735129_F bestätigt?
basis_anzeige_mlYesEindeutig als Basisdosiermenge des benutzten Behälters abgelesener Displaywert. 0, wenn nicht erfasst.
aktuelle_ladung_kgYesSeparat festgehaltene trockene Beladung für den aktuellen Lauf. 0 bei unbekannt.
packungswert_bezugYesStammt der Vergleichswert aus der aktuellen Verpackung für 4,5 kg normal verschmutzte Wäsche und die örtliche Wasserhärte?
vergleich_packung_mlYesDosierempfehlung der Packung für genau den beschriebenen Bezug. 0 bei unbekannt.

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 a useful conceptual boundary by contrasting the base setting with an actual cycle dose. It does not disclose what the tool produces (no output schema exists), nor how the 'offen'/'abweichend' enum states affect the outcome, which is the main behavioral gap.

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 distinguishing statement is placed at the end as a clarifying contrast. The device/model prefix is redundant with the tool name but is needed to disambiguate within a large sibling catalog, so it earns its place.

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?

All five parameters are required and richly documented, and annotations cover the read-only nature, so the agent can assemble the call. What is missing is any indication of the returned comparison outcome, which matters for a tool whose whole purpose is a reconciliation decision and which has no output schema.

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 each of the five parameters carries a detailed German explanation including ranges, enum meanings and 0-as-unknown conventions. The description adds almost nothing beyond that, merely echoing the 4.5 kg / normally soiled reference, so the baseline of 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 specific device (WGB244A40), a specific setting (i-DOS Basisdosierung for 4.5 kg normally soiled laundry) and a specific operation (reconcile with the package figure). The trailing clause 'Distinguish the Bosch base setting from an actual cycle dose' clearly separates this from a dose-application tool. It falls short of 5 because the opaque German compound name plus the vague verb 'abgleichen' leave the actual result of the call (a comparison verdict? a corrected value?) unstated.

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 phrase 'mit Packung abgleichen' implies the situation in which to use it (a package dosing recommendation exists and must be checked against the displayed base dose). However, no explicit when-not condition is given and no sibling is named as the alternative for, e.g., refilling or container-change scenarios, even though several closely related idos_* siblings exist.

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