Skip to main content
Glama

getecoback-climate-weather

saugwischer_pflegeauftrag_annahmekette

Read-only

Nach bestätigter Geräteabgabe fehlende Annahme und anstehende Pflege getrennt erkennen — Track acceptance of the floor-washer cleanup job separately from physical return.

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": {
      "geraet_zurueck": "<geraet_zurueck>",
      "pflege_offen": "<pflege_offen>",
      "uebernahme_bestaetigt": "<uebernahme_bestaetigt>",
      "person_vor_fristeindeutig": "<person_vor_fristeindeutig>"
    },
    "name": "saugwischer_pflegeauftrag_annahmekette"
  }
}

Input Schema

NameRequiredDescriptionDefault
pflege_offenYesEin laut Anleitung nach der Nutzung erforderlicher Pflegeschritt ist offen.
geraet_zurueckYesDie zuletzt nutzende Person hat das Gerät zum vereinbarten geeigneten Ort zurückgebracht.
uebernahme_bestaetigtYesEine andere Person hat genau diesen nötigen Schritt übernommen.
person_vor_fristeindeutigYesFür die Übernahme ist auch ein geeigneter Zeitpunkt vor dem nächsten Lauf bestätigt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the bar is lower. The description adds only the handover precondition and the conceptual split between return and acceptance; it never says what the tool computes or returns from the four booleans, which is the main behavioral question for a read-only classifier.

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?

It is short and the precondition is front-loaded. The German sentence and the English sentence say essentially the same thing, which is mild redundancy rather than waste, so it stays efficient overall.

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?

For a four-required-parameter, read-only tool with no output schema, the description leaves the return semantics entirely unexplained, which is the key gap. Safety and parameter meaning are adequately covered by annotations and schema, so the definition is workable but not complete.

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 every parameter carries a precise German description, so the schema does the heavy lifting and the baseline is 3. The description contributes no additional meaning about how the four booleans interact or which combinations are meaningful.

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 names a concrete action (tracking acceptance of a cleanup job) and a specific resource (the floor-washer handover), and it explicitly separates two states: missing acceptance versus pending care. It does not differentiate against any of the many sibling saugwischer_* tools, so it falls short of a 5.

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?

'Nach bestätigter Geräteabgabe' implies a precondition (only call after the handover is confirmed), which is a usable trigger. However, there is no statement of when not to use it, no named alternative among the numerous related tools, and no explanation of what an agent should do with the result.

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