Skip to main content
Glama

getecoback-raumklima

dampfreiniger_sc3_nachfuellen_arbeitszeit_beleg

Read-only

Trenne die belegte Nachfüllmöglichkeit des SC 3 EasyFix von tatsächlich beobachteter Arbeitszeit — Separate the SC 3 refill feature from measured working time

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": {
      "artikel_15136500": "<artikel_15136500>",
      "durchgang_min": "<durchgang_min>",
      "startphase_min": "<startphase_min>",
      "nachfuellen_min": "<nachfuellen_min>",
      "vollstaendig_protokolliert": "<vollstaendig_protokolliert>"
    },
    "name": "dampfreiniger_sc3_nachfuellen_arbeitszeit_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
durchgang_minYesGesamtdauer eines eigenen vollständig protokollierten Durchgangs
startphase_minYesDavon Minuten vor Beginn der Reinigungsaufgabe
nachfuellen_minYesWeitere Minuten mit Nachfüllen, in denen die Aufgabe stillstand
artikel_15136500YesSC 3 EasyFix in der Ausführung 1.513-650.0 bestätigt
vollstaendig_protokolliertYesDie beiden Teilzeiten sind ohne Überschneidung erfasst und andere Pausen sind ausgeschlossen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. The description adds the domain semantics of separating refill minutes from working time, but does not disclose how incomplete protocol flags are handled, what the result represents, or any error behavior for inconsistent minute values.

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 verb and contains no filler. The German/English duplication is slightly redundant but serves clarity rather than padding.

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?

With five required, fully documented parameters and no output schema, the description should ideally state what the separation yields (e.g., the computed working time) and how the boolean confirmation gates the result. It covers the conceptual intent but leaves the output and edge-case behavior underspecified.

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 five parameters, including the boolean confirmation flags and minute fields, are already well documented in the schema. The description adds no parameter-level detail beyond that baseline, which is acceptable but not enriching.

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 names a specific verb ('Trenne'/'Separate') and domain objects (SC 3 EasyFix refill feature vs. measured working time), which is more than a restatement of the name. However, it remains unclear what the tool actually produces — whether it computes net working time, validates a record, or simply stores a separation — so an agent cannot fully predict the operation from the description alone.

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 phrasing implies a scenario: use this when documented refill time must be distinguished from actually observed working time. There is no explicit 'use when' statement, no exclusions, and no named alternative among the many sibling 'beleg' tools, leaving selection to inference.

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