Skip to main content
Glama

getecoback-raumklima

duschplatz_abziehen_und_kante_getrennt_uebergeben

Read-only

Gemeinsame Badpflege an Duschfläche und Rand gezielt quittieren — Separate the squeegee pass from the edge-wipe handover.

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": {
      "flaechen_belegt": "<flaechen_belegt>",
      "abziehen": "<abziehen>",
      "kante": "<kante>",
      "neu_benetzt": "<neu_benetzt>"
    },
    "name": "duschplatz_abziehen_und_kante_getrennt_uebergeben"
  }
}

Input Schema

NameRequiredDescriptionDefault
kanteYesBeobachteter Abschluss an der vorgesehenen Kante.
abziehenYesBeobachteter Abschluss am vorgesehenen Duschwandabschnitt.
neu_benetztYesWurde der Arbeitsbereich nach der Abschlussmeldung erneut benutzt und benetzt?
flaechen_belegtYesSind die tatsächlich zu pflegenden Flächen und der zulässige Ablauf bekannt?

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 already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, but the description adds almost nothing on top: it does not explain what 'quittieren' actually produces, whether a confirmation is recorded anywhere, or how a 'neu_benetzt' re-wetting event invalidates the acknowledgement. There is also mild tension between the administrative verb 'quittieren' (acknowledge/commit) and readOnlyHint=true, which the description never resolves.

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 single sentence is short and front-loads the resource ('Gemeinsame Badpflege an Duschfläche und Rand'), which is good. However, the bilingual duplication of the same phrase adds length without adding information, and the dash-clause is too compressed to convey the actual operation.

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 tool with four required parameters, an all-enum observation model, and no output schema, the description is too thin: an agent cannot tell what a successful call means, what happens when an observation is 'offen' or 'abweichend', or how the re-wetting flag changes the outcome. Annotations cover the read-only nature but not the workflow context this tool clearly sits in.

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%, with all four parameters (including two enums) documented in the schema, so the baseline applies. The description contributes no extra semantics — it never clarifies what distinguishes 'bestaetigt' from 'abweichend' in practice or how the two observation points are combined into a single verdict.

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 names an action ('gemeinsame Badpflege ... gezielt quittieren' / acknowledge the shower care) and a scope (Duschfläche vs. Rand), but 'quittieren' is metaphorical and the English gloss 'Separate the squeegee pass from the edge-wipe handover' restates the compound name rather than defining the operation. No title is provided, so the agent must infer that this is a confirmation/assessment step from the parameter names alone. Sibling differentiation is only implicit via the recurring 'getrennt' pattern.

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?

No statement of when to call this versus the many similarly named 'getrennt' siblings, and no prerequisites such as 'the surfaces and drain must already be known' (which the schema requires as flaechen_belegt). The agent gets no trigger condition, no exclusions, and no alternative routing.

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