Skip to main content
Glama

getecoback-raumklima

saugwischer_pflegestelle_entnahmeraum

Read-only

Entnahmeraum für Tank und Rolle am vorgesehenen Pflegeplatz prüfen — Check measured tank and roller access at a wet-cleaner service spot.

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": {
      "benoetigt_oben_cm": "<benoetigt_oben_cm>",
      "frei_oben_cm": "<frei_oben_cm>",
      "benoetigt_seite_cm": "<benoetigt_seite_cm>",
      "frei_seite_cm": "<frei_seite_cm>",
      "zugriff_dokumentiert": "<zugriff_dokumentiert>"
    },
    "name": "saugwischer_pflegestelle_entnahmeraum"
  }
}

Input Schema

NameRequiredDescriptionDefault
frei_oben_cmYesTatsächlich freier Raum über dem Gerät an der Pflegestelle.
frei_seite_cmYesTatsächlich freier seitlicher Raum an der Pflegestelle.
benoetigt_oben_cmYesGemessener Platz nach oben für die vorgesehene Tankentnahme.
benoetigt_seite_cmYesGemessener seitlicher Platz zum Entnehmen der Rolle laut Anleitung.
zugriff_dokumentiertYesEntnahmerichtungen stimmen mit der genauen Anleitung überein?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. The description adds that this compares required clearance against actually free clearance for both top and side access, but it does not say what the outcome means (pass/fail thresholds) or what a false zugriff_dokumentiert implies.

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?

A single front-loaded sentence with the key subject first. The German and English halves are semantically identical, so roughly half the text is duplicated, but nothing is padded or irrelevant.

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 read-only measurement-check tool with no output schema, the description should at least indicate what verdict the agent gets back or how the required-vs-free comparison is resolved. It explains the inputs' purpose but leaves the result semantics implicit.

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%, so each of the five parameters is already documented in the schema. The description only restates the tank/roller and service-spot framing, adding no syntax, units beyond cm, or interpretation rules beyond what the schema provides; baseline 3 applies.

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?

States a specific verb (prüfen/check) and a specific resource (Entnahmeraum für Tank und Rolle am vorgesehenen Pflegeplatz), so an agent knows this is a clearance-verification check for wet-cleaner service spots. It does not name or contrast with any sibling check such as tineco_saugwischer_pflegecheck, so differentiation is left to the name alone.

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 when-to-use or when-not-to-use guidance and no mention of alternative checks in the saugwischer_* family. The phrase 'am vorgesehenen Pflegeplatz' implies the scenario but gives no prerequisites, ordering, or exclusion criteria.

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