Skip to main content
Glama

getecoback-raumklima

pflege_ungeplante_abgaenge_trockene_reserve

Read-only

Für einen abgebrochenen Pflegeschritt zwischen bestätigtem Ersatz und offenem Rücklauf unterscheiden — Keep replacement stock separate from incomplete items after a care interruption.

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": {
      "freigaben_belegt": "<freigaben_belegt>",
      "abschnitt_bedarf": "<abschnitt_bedarf>",
      "eingesetzt": "<eingesetzt>",
      "unabh_reserve": "<unabh_reserve>",
      "unterbrochene_pflege": "<unterbrochene_pflege>"
    },
    "name": "pflege_ungeplante_abgaenge_trockene_reserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
eingesetztYesBereits passend in diesem Abschnitt eingesetzte Teile.
unabh_reserveYesWeitere bestätigte saubere und passende Teile.
abschnitt_bedarfYesTeile des betrachteten Typs für den nächsten Abschnitt.
freigaben_belegtYesSind die konkreten Ersatzteile geprüft und bereits für den Einsatz bereit?
unterbrochene_pflegeYesWeitere Teile, die nach Unterbrechung erst geprüft werden müssen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/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 and the description need not repeat it. However, it adds nothing about what the computation produces, whether results are a count, a split of reserve versus incomplete items, or how the required boolean gate (freigaben_belegt) changes the outcome — and there is no output schema to compensate.

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?

Two short clauses with no padding, which is appropriately sized. The cost is a redundant bilingual restatement where the English gloss is not a translation but a paraphrase, and the front-loaded German clause is the more opaque of the two.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Five required parameters, no output schema, and no explanation of the return value or of the arithmetic relationship between eingesetzt, unabh_reserve, abschnitt_bedarf, and unterbrochene_pflege. For a pure computation tool the description must supply the input-to-output contract, and it does not.

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% with all five parameters individually documented in German, so semantics are already carried by the schema. The description adds only the framing of "bestätigtem Ersatz" versus "offenem Rücklauf", which loosely maps to freigaben_belegt/unabh_reserve versus unterbrochene_pflege but gives no indication of how the numbers combine.

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

Purpose2/5

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

The description restates the tool name in abstract terms ("für einen abgebrochenen Pflegeschritt ... unterscheiden") without stating a concrete verb-and-resource operation. The English gloss "keep replacement stock separate from incomplete items" hints at a classification of stock, but an agent cannot determine from this whether the tool computes a quantity, returns a boolean, or performs a move.

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?

The phrase "after a care interruption" implies a triggering scenario, but there is no statement of when to call this versus the many sibling pflege_* tools, and no exclusions or prerequisites. No alternative is named even though the sibling list is dense with near-identical pflege tools.

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