Skip to main content
Glama

getecoback-raumklima

bosch_mixfuss_trocknen_lagerung_befund

Read-only

Erfasst, ob ein gereinigter Bosch Mixfuß gemäß seiner Anleitung aufrecht abtropfte und anschließend trocken beobachtet wurde — Record upright draining and subsequent dryness separately for a Bosch blending shaft.

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": {
      "e_nummer": "<e_nummer>",
      "aufrecht_messer_oben": "<aufrecht_messer_oben>",
      "trockenheit_beobachtet": "<trockenheit_beobachtet>"
    },
    "name": "bosch_mixfuss_trocknen_lagerung_befund"
  }
}

Input Schema

NameRequiredDescriptionDefault
e_nummerYesVollständige deutsche Bosch E-Nr. einschließlich Index.
aufrecht_messer_obenYesAbtropfposition aufrecht mit Messer nach oben belegt?
trockenheit_beobachtetYesAnschließend als trocken beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only and closed-world annotations, the description adds meaningful evidentiary behavior: upright draining must be considered against the appliance instructions, and later dryness is a separate observation rather than something inferred from draining. It does not explain what finding is produced or how unresolved evidence affects that finding.

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?

The definition is short and front-loads the appliance and the two facts being assessed. Its bilingual wording partly repeats itself, although the English addition of “separately” contributes a useful constraint.

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

Completeness4/5

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

For a small three-input assessment, the description and fully specified enum schema provide enough information to select and populate the tool. With no output schema, however, it would benefit from stating the returned Befund and explaining “offen,” especially since the storage conclusion implied by the tool name is not described.

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%, with all three required parameters constrained by enums, so the schema does most of the parameter documentation. The description adds sequence, manual alignment, and separation of observations, but largely restates the two observation fields and adds nothing about the E-Nummer choices or the shared value “offen.”

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 gives a concrete resource and scope: recording upright draining and subsequent dryness for a cleaned Bosch blending shaft. The narrow subject helps distinguish it from the siblings, but it provides no explicit differentiation from the other Bosch Mixfuß tools.

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

Usage Guidelines4/5

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

“Gereinigter,” “gemäß seiner Anleitung,” and “anschließend” establish that this is for post-cleaning drying evidence assessed in sequence. Recording the two observations separately is useful invocation guidance, although there are no exclusions, prerequisites for unresolved evidence, or named alternatives.

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