Skip to main content
Glama

getecoback-raumklima

kompaktspuel_gemessener_wasseranteil_separater_pflichtteile

Read-only

Weist den Anteil der getrennten Bearbeitung von nicht mitgeladenem Pflichtgeschirr am gemessenen Aufgabenwasser aus — Attribute measured water to required items omitted from the compact load.

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": {
      "maschine_l": "<maschine_l>",
      "ergaenzung_l": "<ergaenzung_l>",
      "ergaenzung_belegt": "<ergaenzung_belegt>",
      "aufgabe_fertig": "<aufgabe_fertig>"
    },
    "name": "kompaktspuel_gemessener_wasseranteil_separater_pflichtteile"
  }
}

Input Schema

NameRequiredDescriptionDefault
maschine_lYesGemessene Liter für den eigenen Maschinenlauf.
ergaenzung_lYesGetrennt dokumentierte Liter für dabei nicht eingelegte Pflichtstücke.
aufgabe_fertigYesDas ganze benötigte Geschirr ist tatsächlich bereitgestellt, ohne offenen weiteren Wasserweg.
ergaenzung_belegtYesDie getrennte Menge ist tatsächlich gemessen und betrifft genau die nicht eingelegten Pflichtstücke.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint/openWorldHint annotations already signal a pure computation with no side effects, so the description's burden is lighter. It adds the notion that the result is an attribution of measured water, but says nothing about how the share is expressed, what happens when ergaenzung_belegt is false, or how conflicting inputs are resolved. With no output schema, that gap matters more than it otherwise would.

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, front-loaded sentence that leads with the computed quantity before the parenthetical gloss. It is dense with domain jargon but contains no filler or redundancy.

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 four required parameters are described and annotations cover the safety profile, so the call mechanics are adequate. However, with no output schema and no statement of the return form or edge-case behaviour (unverified separate quantity, unfinished task set), the definition leaves the agent guessing about results for a computation tool.

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 schema, which sets the baseline at 3. The description reinforces the framing ('gemessenes Aufgabenwasser', 'nicht mitgeladenes Pflichtgeschirr') without adding constraints or interpretation rules beyond what the schema states.

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 uses a specific verb ('Weist ... aus' / 'Attribute') tied to a precise resource: the share of measured task water belonging to required items that were not loaded. An agent can tell this is an allocation/attribution computation rather than a lookup or mutation. It stops short of contrasting itself with the neighbouring Pflichtgeschirr/Teilladung tools, so sibling confusion remains possible.

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 statement of when this tool should be chosen, when it should not, or which sibling handles the adjacent case (e.g. the Pflichtgeschirr provisioning or non-loaded-parts tools). The agent must infer applicability entirely from the topic vocabulary.

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