Skip to main content
Glama

getecoback-raumklima

duschhalter_wiederholte_handhabung_ausgelassene_faelle

Read-only

Bei einer eigenen Ablagebeobachtung vollständig erfasste Handgriffe von ausgelassenen Fällen trennen — Quantify handling evidence without mistaking skipped attempts for successful 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": {
      "beabsichtigte_faelle": "<beabsichtigte_faelle>",
      "beobachtet_ohne_wechsel": "<beobachtet_ohne_wechsel>",
      "beobachtet_mit_wechsel": "<beobachtet_mit_wechsel>",
      "vorab_regeln_gleich": "<vorab_regeln_gleich>"
    },
    "name": "duschhalter_wiederholte_handhabung_ausgelassene_faelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorab_regeln_gleichYesJeder Fall wurde nach denselben vorher festgelegten Beobachtungsregeln bewertet.
beabsichtigte_faelleYesZuvor festgelegte Anwendungsfälle im Beobachtungsblock.
beobachtet_mit_wechselYesVollständig beobachtet, mit einem unerwarteten Wechsel des Ablaufs.
beobachtet_ohne_wechselYesVollständig beobachtet, ohne unerwartet den Ablauf wechseln zu müssen.

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?

The annotations already establish that this is a read-only, non-open-world operation. The description adds interpretive context that skipped attempts must not be counted as successful use, but it does not explain the calculation, assumptions, or what kind of result is returned.

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 compact and front-loads the observation context before the quantifying purpose. The bilingual restatement is slightly redundant, but every part remains relevant and there is no bloated explanation.

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?

The tool has four required parameters and no output schema, yet the description does not explain the resulting quantity or how the separated counts are reported. It is adequate for understanding the intent, but incomplete for confidently invoking an analytical tool whose return value is undocumented.

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 four parameters are already documented in the input schema. The description adds no parameter-specific meaning beyond the schema, which is acceptable at the baseline for full schema coverage.

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 operation: separating fully captured handling actions from omitted cases in an observation, and quantifying handling evidence. The verb-and-resource pairing is clear enough for an agent to understand the analytical purpose, though it does not explicitly distinguish itself from the many other shower-holder sibling tools.

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?

The phrase 'Bei einer eigenen Ablagebeobachtung' implies the context in which the tool applies, namely one's own observation data. However, it gives no explicit when-not guidance, prerequisites, or comparison to 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