Skip to main content
Glama

getecoback-climate-weather

pflege_flurschrank_abholfach_nicht_entleert

Read-only

In einem gemeinsamen Abholfach Nachschub erst bei wirklich quittierter Abholung einplanen — Check a cleared pickup cubby before adding the next owner’s textile group.

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": {
      "zustand_und_fach_geprueft": "<zustand_und_fach_geprueft>",
      "fach_plaetze": "<fach_plaetze>",
      "erster_belegt": "<erster_belegt>",
      "erste_abgeholt": "<erste_abgeholt>",
      "zweite_gruppe": "<zweite_gruppe>",
      "klare_resttrennung": "<klare_resttrennung>"
    },
    "name": "pflege_flurschrank_abholfach_nicht_entleert"
  }
}

Input Schema

NameRequiredDescriptionDefault
fach_plaetzeYesGeprüfte nutzbare Plätze in diesem Fach.
erster_belegtYesDavon für die erste Abholung bereits bereitgelegte Stücke.
zweite_gruppeYesStücke der zweiten Gruppe, die bereitgelegt werden sollen.
erste_abgeholtYesDavon nachweislich abgeholt.
klare_resttrennungYesKann anhand geeigneter getrennt markierter Bereiche neben der ersten Restgruppe abgelegt werden?
zustand_und_fach_geprueftYesSind das Fach, die trockenen Stücke und die jeweiligen Zuordnungen überprüft?

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. The description adds a vague gating condition but does not explain what the check returns, what happens when the cubby is not cleared, or how the six required inputs determine the 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 not front-loaded; mixing German and English and combining a planning rule with a check makes the single sentence hard to parse and somewhat redundant.

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?

For a six-required-parameter validation/check tool with no output schema and only minimal annotations, the description is incomplete: it does not explain the validation outcome, the boolean flags, or how the counts determine whether the next textile group fits.

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?

All six parameters have schema descriptions (100% coverage), so the schema carries the semantic load. The description adds no parameter-specific meaning beyond that baseline.

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 mixes planning ('Nachschub ... einplanen') with checking ('Check a cleared pickup cubby') without stating a clear verb+resource. Its English phrase 'cleared pickup cubby' also conflicts with the tool name's 'nicht entleert' (not emptied), so an agent cannot reliably tell what the tool actually does.

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?

It implies the check should happen only after confirmed pickup ('erst bei wirklich quittierter Abholung'), but gives no explicit when-to-use / when-not-to-use guidance and names no alternatives among the sibling 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