Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_rundung_eingabeschritt_gewichtsgrenze

Read-only

Bei Automatikprogrammen das gemessene Portionsgewicht von der gerundeten Eingabe unterscheiden — Keep rounded programme input separate from measured food weight.

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": {
      "handbuch_belegt": "<handbuch_belegt>",
      "programm": "<programm>",
      "gewogen_g": "<gewogen_g>",
      "eingegeben_g": "<eingegeben_g>"
    },
    "name": "bosch_bfl524_rundung_eingabeschritt_gewichtsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
programmYesProgramm laut Display.
gewogen_gYesTatsächlich gewogenes Lebensmittelgewicht in g.
eingegeben_gYesTatsächlich auswählbarer und eingegebener Displaywert in g.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 and the description is not required to restate it. The description adds only the framing that automatic programmes are involved; it says nothing about what is returned, whether the two weights are merely compared or checked for consistency, or what happens when the roundings disagree — all relevant for a tool with no output schema.

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 bilingual sentence with no padding, and the qualifying condition (automatic programmes) is front-loaded. The German/English duplication adds a little length but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four required parameters, an enum, and no output schema mean the description needs to explain what the call produces and how the two weights are used — it does neither. For a read-only tool whose entire value is a comparison result, leaving the return undefined is a substantive gap.

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 the field descriptions already spell out gewogen_g (actually weighed food weight) versus eingegeben_g (selectable display value), so the baseline is 3. The description reinforces that conceptual split, which is genuine but marginal added value since the schema already carries it, and it says nothing about the programm enum or the handbuch_belegt gate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a topic — keeping rounded programme input separate from measured food weight — but never says what the tool actually does with the four arguments it requires. 'Unterscheiden' is a cognitive task, not a tool action (lookup? validation? returns a comparison?), so an agent cannot tell what calling it produces, and nothing distinguishes it from siblings like bosch_sks62e32eu_eco50_quellenwerte_rundung or messreihe_grenzwert_rundung_faelle.

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?

'Bei Automatikprogrammen' implies the domain (automatic programmes only), which is a faint usage signal, but there is no statement of when to choose this tool over the many rounding-related siblings and no exclusions or prerequisites beyond the contextual hint.

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