Skip to main content
Glama

getecoback-raumklima

pflege_einsatzort_erst_nach_trockenablage_wechseln

Read-only

Ein teilfertiges Pflegeset nur mit geeignetem getrennten Platz in einen zweiten Raum verlagern — Decide whether a care-in-progress kit can be staged in another room.

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": {
      "fuer_kurzzeit_bestaetigt": "<fuer_kurzzeit_bestaetigt>",
      "trockene_teile": "<trockene_teile>",
      "offene_teile": "<offene_teile>",
      "ziel_trockenplaetze": "<ziel_trockenplaetze>",
      "ziel_offenplaetze": "<ziel_offenplaetze>"
    },
    "name": "pflege_einsatzort_erst_nach_trockenablage_wechseln"
  }
}

Input Schema

NameRequiredDescriptionDefault
offene_teileYesTeile in noch offenem feuchtem oder ungeklärtem Zustand.
trockene_teileYesEinzeln geprüfte trockene Teile.
ziel_offenplaetzeYesFür diese offenen Teile ausdrücklich geeignete, separat geführte Plätze.
ziel_trockenplaetzeYesPassende getrennte trockene Plätze im Zielraum.
fuer_kurzzeit_bestaetigtYesErlaubt der dokumentierte Ablauf eine Zwischenablage dieser Teile?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description's opening 'verlagern' implies a mutation, which the second clause then walks back to a decision — that inconsistency is not resolved, and there is no statement about what the decision depends on (capacity checks, separation rules) or what the tool does with a partial/blocked outcome.

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?

It is short, but it is effectively the same sentence twice in two languages, and the German version is front-loaded with the misleading 'verlagern' verb while the clarifying 'Decide whether' only arrives second. The duplication costs space without adding information.

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?

With five required parameters and no output schema, the description needs to indicate what the agent gets back — a yes/no verdict, a reason, a constraint violation. It says nothing about the result or about how a negative decision should be interpreted, leaving a real gap for a decision 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% and each of the five parameters carries a precise German definition, so the schema does all the semantic work. The description neither restates nor enriches any parameter meaning, which is the baseline expectation when the schema is this well documented.

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 English gloss ('Decide whether a care-in-progress kit can be staged in another room') states a recognizable decision, but the German lead clause uses 'verlagern' (relocate), which reads as a physical move rather than an evaluation. The two halves pull in different directions, so an agent cannot tell from the text alone whether this performs an action or renders a verdict.

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 name hints at a sequencing rule ('erst nach Trockenablage'), but the description never states when to call this versus other care-kit tools, nor any precondition such as needing a confirmed short-term staging step. The sibling list is not invoked or differentiated anywhere in the text.

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