Skip to main content
Glama

getecoback-raumklima

bosch_ergomixx_fresh_zipbeutel_vorinhalt_wiederverwendung

Read-only

Berücksichtigt beim Bosch Fresh Zip-Beutel den dokumentierten Vorinhalt und den Reinigungs- und Trocknungsstatus — Read Bosch Fresh bag reuse limits from recorded previous contents, cleaning and drying.

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": {
      "system_bestaetigt": "<system_bestaetigt>",
      "vorinhalt": "<vorinhalt>",
      "sauber_und_vollstaendig_trocken": "<sauber_und_vollstaendig_trocken>"
    },
    "name": "bosch_ergomixx_fresh_zipbeutel_vorinhalt_wiederverwendung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorinhaltYesDokumentierte vorherige Lagerung.
system_bestaetigtYesOriginal Bosch Fresh Zip-Beutel aus der passenden Zubehöranleitung bestätigt.
sauber_und_vollstaendig_trockenYesSorgfältige Reinigung und vollständiges Trocknen vor erneuter Nutzung dokumentiert?

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 and the description's 'Read' framing is consistent with that. What the description does not add is behavior in edge cases: what the tool concludes when vorinhalt or sauber_und_vollstaendig_trocken is 'offen', or what a returned limit represents. That leaves the extra-context value modest.

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?

One compact sentence with the subject and resource front-loaded, followed by the relevant state factors. The German/English duplication is largely redundant for an agent but is short and does not bury the key 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?

For a read-only lookup tool with no output schema, the description should clarify what comes back (a boolean verdict, a cycle/limit count, or a rationale) and how undetermined inputs are handled; it only says 'reuse limits'. It is adequate to select the tool but not fully sufficient to interpret its result.

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 documented in the schema, so the schema carries the semantics; the description only paraphrases the three inputs (prior contents, cleaning, drying) without adding interpretation, such as why 'rohes_fleisch_fisch_gefluegel' is treated differently from 'anderer_bekannter_inhalt'. The 3 baseline 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 states a specific verb and resource: retrieving reuse limits for a Bosch Fresh zip bag based on documented prior contents and cleaning/drying status. It is clearly distinguishable from the sibling hardware/compatibility tools in substance, though it never names or contrasts an alternative. The bilingual restatement reinforces rather than obscures the purpose.

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 tool is for judging whether a bag may be reused given its prior contents and its cleaned/dried state. There is no explicit when-to-use vs when-not, no prerequisite statement (e.g. that the original bag must be confirmed via system_bestaetigt), and no alternative tool named for related reuse questions such as geraetepaar_wiederverwendung_gemeinsames_medium.

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