Skip to main content
Glama

getecoback-climate-weather

bosch_ergomixx_fresh_vakuum_behaelter_oder_beutel_anzeige

Read-only

Unterscheidet die dokumentierten Vakuummerkmale beim Bosch Fresh-Behälter und Zip-Beutel — Distinguish the manual’s different vacuum indicators for a Bosch Fresh container and zip bag.

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_bestaetigt": "<modell_bestaetigt>",
      "behaeltertyp": "<behaeltertyp>",
      "beobachtung": "<beobachtung>"
    },
    "name": "bosch_ergomixx_fresh_vakuum_behaelter_oder_beutel_anzeige"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesBereits beobachtetes Merkmal.
behaeltertypYesKomponente der Anleitung.
modell_bestaetigtYesBosch MS6CB61V1/01 und das zugehörige Fresh-System sind belegt.

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 establish this is a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the lower bar applies. The description adds that the answer is grounded in the manual's documented indicators, which is useful, but it says nothing about what comes back (a verdict? a next step?) despite there being 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 front-loaded statement, with the German original followed by an English rendering. It is efficient and readable, though the bilingual duplication is redundant text that does not add information.

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?

Three required parameters and no output schema mean the description should explain what the tool returns and how the result should be used. It covers the inputs' intent adequately but leaves the outcome entirely unspecified.

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 both enums are self-documenting, so the baseline of 3 applies. The description adds only the nuance that the features are "dokumentiert" (manual-derived), without clarifying how a value like "offen" is treated.

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?

"Unterscheidet die dokumentierten Vakuummerkmale" gives a specific verb (distinguish/interpret) and a specific resource (documented vacuum indicators) scoped to Fresh container and zip bag. It is clear enough to separate from siblings such as the compatibility or reuse tools, but it never explicitly names an alternative to distinguish against.

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?

Usage is only implied: the required parameters (confirmed model, container type, observation) sketch the calling context, but the description never states when to call this instead of a sibling, nor what to do if the model is not confirmed or the component is unknown.

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