Skip to main content
Glama

getecoback-raumklima

bosch_msm67170_abschalten_ueberlast_wartezeit

Read-only

Ordnet beim bestätigten Bosch MSM67170 eine Abschaltung während der Nutzung der Abkühlangabe im Handbuch zu — Read the manual’s cooling interval for a confirmed Bosch MSM67170 shutdown during use.

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>",
      "ereignis": "<ereignis>",
      "minuten_seit_aus_und_getrennt": "<minuten_seit_aus_und_getrennt>"
    },
    "name": "bosch_msm67170_abschalten_ueberlast_wartezeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ereignisYesBeobachtetes Ereignis.
modell_bestaetigtYesKonkretes Gerät als MSM67170/02 bestätigt.
minuten_seit_aus_und_getrenntYesBeobachtete Minuten seit Ausschalten und Netztrennung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 by structured data. The description adds that the device must be 'confirmed' as an MSM67170, which usefully ties to the modell_bestaetigt requirement, but it says nothing about what is returned, how unconfirmed models or 'anderer_fehler' events are handled, or whether the answer is a fixed manual value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is compact, but it is delivered as the same statement twice, once in German and once in English, which is redundant rather than additive. The front-loaded German clause is dense and the em-dash construction reads as a run-on, though nothing is truly extraneous beyond the duplication.

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 simple three-parameter read-only lookup with full schema coverage and no output schema, the description covers the essentials of model confirmation and the shutdown condition. It remains thin on what value the tool produces (a cooling interval) and how the three inputs combine, which an agent would want in order to call it with confidence.

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 all three parameters are already documented in the schema, and the baseline is 3. The description reinforces two of them ('bestätigten Bosch MSM67170' for modell_bestaetigt, 'Abschaltung während der Nutzung' for the ereignis enum) but adds no new semantics such as how minuten_seit_aus_und_getrennt affects the assigned interval.

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

Purpose3/5

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

The description does identify the resource (cooling interval from the manual for a confirmed Bosch MSM67170) and the triggering condition (a shutdown during use), so an agent can roughly tell it is a read-only lookup. But the verb phrase 'Ordnet ... zu' ('assigns') is vague about the operation, and the German and English halves are near-duplicates that still leave the actual output (a wait time?) implicit rather than stated.

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 explicit when-to-use or when-not-to-use guidance, and no routing to any alternative. The sibling bosch_msm67170_eis_crush_l_messer_und_menge addresses a different aspect of the same appliance, and nothing here helps an agent choose between them or decide when this lookup is appropriate versus unnecessary.

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