Skip to main content
Glama

getecoback-climate-weather

bodenpflege_kantenwechsel_wechselauflage

Read-only

Markierte Auflagen bei einem beobachteten Wechsel zwischen Arbeitsbereichen getrennt zurücklegen — Check a one-way clean/used transfer at a floor-care boundary.

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": {
      "auflageneinsatz_belegt": "<auflageneinsatz_belegt>",
      "saubere_auflagen": "<saubere_auflagen>",
      "abzugebende_auflagen": "<abzugebende_auflagen>",
      "plaetze_benutzt": "<plaetze_benutzt>",
      "naechster_bedarf": "<naechster_bedarf>"
    },
    "name": "bodenpflege_kantenwechsel_wechselauflage"
  }
}

Input Schema

NameRequiredDescriptionDefault
plaetze_benutztYesFreie gekennzeichnete Plätze für genau diese benutzten Auflagen.
naechster_bedarfYesFrische Auflagen für den nächsten Arbeitsabschnitt.
saubere_auflagenYesJetzt bereitliegende passende Auflagen vor dem Wechsel.
abzugebende_auflagenYesBeim beendeten Abschnitt getrennt zurückzugebende benutzte Auflagen.
auflageneinsatz_belegtYesSind Auflagentausch und Ablagen für den Vorgang und beide Bereiche bestätigt?

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 only declare readOnlyHint=true and openWorldHint=false; the description adds no disclosure of what the check evaluates, what a pass/fail means, or whether the numeric counts must balance. Worse, the leading German verb 'zurücklegen' suggests a physical write while the tool is declared read-only, leaving the agent unsure whether this mutates state or only validates it.

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 a single compact sentence with the resource front-loaded, which is good. However, the bilingual em-dash gloss duplicates rather than clarifies, and the two languages state different things, so the brevity comes at the cost of precision rather than earning its place.

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?

This is a five-parameter, all-required tool with no output schema, so the description must explain what the 'check' returns and what conditions make it succeed or fail — it does neither. Units for the numeric fields (pad counts vs. slot counts) and the meaning of the confirmation boolean relative to the result are left entirely to inference.

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 coverage is 100% and each field carries its own German description (free marked slots, clean pads on hand, pads to return, next-section demand, confirmation boolean), so the schema does the heavy lifting. The description adds no additional meaning such as units, valid ranges, or relationships between the counts, so the baseline 3 applies.

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 German clause 'Markierte Auflagen ... getrennt zurücklegen' names a resource (markierte Auflagen) but the verb is ambiguous — it reads as an action ('place back separately'), while the English gloss resolves it as 'Check a one-way clean/used transfer'. The two halves pull in different directions, and nothing distinguishes this from the many sibling 'bodenpflege_*' probe/check tools.

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 to use this versus the sibling verification tools (e.g. bodenpflege_referenzstellen_gegenprobe, bodenpflege_sichtspuren_trockenprobe), and no prerequisites such as the boundary having been observed or both areas confirmed. The only implicit context is 'bei einem beobachteten Wechsel', which is a condition, not guidance on tool selection.

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