Skip to main content
Glama

getecoback-climate-weather

bosch_kompakt_regeneration_variante_eco_basis

Read-only

Beim deutschen SKS62E32EU Zusatzaufwand für die Regeneration auf die 8-Liter-Eco-Referenz begrenzen — Read the exact compact dishwasher laboratory row, without mapping it onto a calendar.

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": {
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "kurzbeleg_eco_l": "<kurzbeleg_eco_l>",
      "bedingung": "<bedingung>"
    },
    "name": "bosch_kompakt_regeneration_variante_eco_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedingungYesBelegter Bezug für den Vergleich.
kurzbeleg_eco_lYesEco-50-Literangabe aus passender Kurzanleitung oder bestätigtem Modell-Datenblatt.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 structurally, and the description is consistent with a pure read. It adds the useful constraint that no calendar normalization is applied, but says nothing about what the returned row contains, its units, or what happens when the eco value is absent.

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?

It is short — effectively two clauses joined by an em dash — with no filler sentences. However, the switch between German and English within a single sentence and the dense nominal style make it harder to parse than a plain front-loaded statement of purpose would be.

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 three required, fully documented parameters and no output schema, an agent can technically fill the call from the schema alone, and the read-only annotation covers safety. What is missing is any statement of what the returned laboratory row looks like or how to interpret a low or missing eco value, which matters for a domain-specific lookup.

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 three parameters (anleitung_bestaetigt, kurzbeleg_eco_l, bedingung) are already documented in the schema, which sets the baseline at 3. The description only loosely gestures at the 8-liter eco reference corresponding to kurzbeleg_eco_l; it adds no meaning about the enum options or the confirmation flag.

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 second clause gives a concrete verb and resource ("Read the exact compact dishwasher laboratory row") and anchors it to the German model SKS62E32EU and the 8-liter eco reference, so the resource is identifiable. But the leading German clause is cryptic jargon ("Zusatzaufwand für die Regeneration ... begrenzen") and never states plainly that this returns an eco reference value for a compact dishwasher, nor does it distinguish itself from the many sibling bosch_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is one implicit exclusion — "without mapping it onto a calendar" — which hints at a boundary, but no named alternative sibling and no clear statement of when an agent should pick this tool over, say, eco_raeumdaten_quellenangabe or spuelmaschine_eco_sperrzeit_budget. The user must infer the scenario entirely from the model number in the first clause.

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