Skip to main content
Glama

getecoback-raumklima

braun_zerkleinerer_laufzeit_pause_erst_nach_dokumentiertem_ende

Read-only

Vergleicht protokollierte Laufzeit und bereits verstrichene Pause mit der Handbuchzeile ca oder mc — Compare a recorded chopper run and elapsed pause with the matching ca or mc manual row.

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": {
      "motor": "<motor>",
      "code": "<code>",
      "laufzeit_s": "<laufzeit_s>",
      "pause_s": "<pause_s>",
      "ende_bestaetigt": "<ende_bestaetigt>"
    },
    "name": "braun_zerkleinerer_laufzeit_pause_erst_nach_dokumentiertem_ende"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesKennzeichen des vorhandenen Zerkleinerers.
motorYesExaktes Gerät der deutschen Braun Unterlage.
pause_sYesDokumentierte Sekunden seit vollständigem Ende dieses Laufs.
laufzeit_sYesDokumentierte Sekunden des unmittelbar vorigen zusammenhängenden Laufs.
ende_bestaetigtYesDer vollständige Stillstand am Ende ist dokumentiert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 consistent with it (a pure comparison against a manual row). What is missing is behavior the annotations cannot convey: no output schema exists, yet the description never says what the comparison yields (a boolean verdict, a matching table row, a deviation flag), which is the single most important unknown for a decision tool.

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 that front-loads the operation and appends the manual-row qualifier; nothing is padded or buried. The German/English duplication costs a little space but is defensible in a mixed-language toolset.

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?

All five parameters are documented in the schema, but the tool is a comparison whose result is the point, and with no output schema the description should state what comes back and how mismatches are represented. The role of "offen"/ende_bestaetigt in gating a valid comparison is also left unstated, leaving moderate gaps for a tool whose name suggests a specific documented-end precondition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description genuinely adds meaning by tying the `code` parameter to the concept of the manual row ("Handbuchzeile ca oder mc"), clarifying that the enum selects a table row rather than a device variant. It does not explain the "offen" enum values or how laufzeit_s and pause_s interact with that row, so it stops short of full value.

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 names a specific operation ("Vergleicht protokollierte Laufzeit und bereits verstrichene Pause") and its reference target ("mit der Handbuchzeile ca oder mc"), so the agent knows exactly what is being compared against what. It does not, however, differentiate itself from similarly named Braun chopper siblings such as the ca/mc/hc/bc Behälterkennzeichen tool, leaving the agent to infer the boundary.

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 reader infers this is the tool for checking a documented run-and-pause against the manual table, but there is no explicit when-to-use statement, no prerequisite (e.g. complete standstill must be confirmed first), and no alternative named. The required parameter ende_bestaetigt hints at a precondition, but the description never states it.

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