Skip to main content
Glama

getecoback-raumklima

pflege_tiefenwechsel_reinigung_oberhalb_boden

Read-only

Beobachtete Boden-Nacharbeit vermeiden, indem freigegebene obere Pflegeschritte passend zur Bodenrunde abschließen — Check whether overhead work overlaps a finished floor pass.

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": {
      "abfolge_zulaessig": "<abfolge_zulaessig>",
      "oben_ende": "<oben_ende>",
      "boden_start": "<boden_start>",
      "boden_dauer": "<boden_dauer>",
      "fenster_ende": "<fenster_ende>"
    },
    "name": "pflege_tiefenwechsel_reinigung_oberhalb_boden"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_endeYesGeplantes Ende der betroffenen oberen Arbeiten einschließlich Rückstände aufnehmen.
boden_dauerYesBeobachtete Arbeitsdauer für genau diesen Abschnitt.
boden_startYesBeginn des vorgesehenen Bodenabschnitts darunter.
fenster_endeYesLetzte mögliche Tagesminute für das Ende der Bodenarbeit.
abfolge_zulaessigYesDürfen die betrachteten Pflegeschritte verändert angeordnet werden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

The annotations declare readOnlyHint=true and openWorldHint=false, consistent with the word 'Check'. The description adds the domain intent of avoiding rework, but it does not explain what the check returns, how 'abfolge_zulaessig' changes the outcome, or what happens on a negative result.

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?

The description is short, but it mixes German and English and front-loads a purpose clause rather than the operation. The English sentence is the useful part; the German preamble is harder to parse and does not add routing value.

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 five-required-parameter validation tool with no output schema, the definition does not explain the decision logic or expected return. An agent knows it is a check but not how the numeric inputs combine to produce a result.

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 five parameters have 100% schema description coverage. The description adds no parameter-level meaning, units, or relationship guidance beyond the schema, so the baseline of 3 is appropriate.

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 description opens with a goal ('avoid floor rework') and an English gloss ('Check whether overhead work overlaps a finished floor pass'). It identifies a check, but the exact resource and decision boundary remain fuzzy, and it does not differentiate from the many pflege_* sibling 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 explicit when-to-use, prerequisite, or alternative guidance. The goal statement implies it is for coordinating overhead versus floor passes, but an agent gets no routing instructions versus sibling pflege_* sequence 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