Skip to main content
Glama

getecoback-raumklima

bosch_sks62e32eu_eco50_quellenwerte_rundung

Read-only

Liest die getrennten Eco-50-Angaben pro Zyklus und pro 100 Zyklen für diesen deutschen Kompaktspüler — Read the exact model’s Eco 50 per-cycle figures and its rounded 100-cycle label.

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": {
      "modell_de_belegt": "<modell_de_belegt>",
      "bezug": "<bezug>"
    },
    "name": "bosch_sks62e32eu_eco50_quellenwerte_rundung"
  }
}

Input Schema

NameRequiredDescriptionDefault
bezugYesFür welchen Fall sollen die Angaben gelten?
modell_de_belegtYesDeutsche Produktunterlage und genau der SKS62E32EU sind abgeglichen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safe-read profile is covered. The description usefully adds that the figures are separated per cycle and per 100 cycles and that the label value is rounded. However, it is silent on the most consequential behavior: what happens when modell_de_belegt is false, i.e. whether values are withheld, flagged, or returned anyway.

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?

A single front-loaded sentence with the German statement first and an English restatement, which aids bilingual callers. The em-dash construction is slightly awkward and the bilingual duplication is redundant, but nothing is padded.

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 two-parameter read-only tool with no output schema, the description covers what is read and for which model. It does not describe the return shape (units, whether both values come back together, what rounding is applied) or the consequence of the required confirmation boolean. Those gaps matter because there is no output schema to compensate.

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 the schema already explains both parameters, and the baseline is 3. The description does add a little meaning by tying the output to per-cycle versus 100-cycle figures, which hints at the bezug enum values (eco50_label vs anderes_programm). It adds no explanation of the boolean gate's effect beyond what the schema states.

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 states a specific verb and resource: 'Liest die getrennten Eco-50-Angaben pro Zyklus und pro 100 Zyklen' for a named model (SKS62E32EU). It clearly separates the per-cycle figure from the rounded 100-cycle label, which is a meaningful distinction an agent can act on. It does not explicitly contrast itself with sibling tools such as the label-rounding or rounding-cases tools, so it stops short of a 5.

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 no when-to-use or when-not-to-use guidance. The description never says how this differs from related tools (e.g. label rounding distance or limit-value rounding cases) or under which conditions the caller should pick it. The only implied scoping is the model name and the Eco-50 program, which the agent must infer.

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