Skip to main content
Glama

getecoback-raumklima

saugwischer_bodenfreigabe

Read-only

Boden- und Gerätefreigabe für aktive Nassreinigung abgleichen — Check both floor and wet-cleaner permissions before use.

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": {
      "floor": "<floor>",
      "equipment": "<equipment>",
      "damage": "<damage>"
    },
    "name": "saugwischer_bodenfreigabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
floorYesFreigabe des Bodenherstellers.
damageYesOffene Fugen, beschädigte Versiegelung oder andere sichtbare Schäden?
equipmentYesFreigabe der genauen Geräteanleitung für Boden und Betriebsart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the non-mutating, closed-world behavior is covered. The description reinforces the check-before-use safety context but does not explain how 'unknown' answers or 'damage=yes' affect the release, nor what result is returned.

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?

The description is compact and front-loads the German purpose before the English gloss. The bilingual restatement is mildly redundant but does not add unnecessary detail.

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?

Inputs are fully documented and the read-only annotation covers safety, but no output schema exists, so the description should ideally say what a successful or failed release looks like and how 'unknown' values are treated. It covers the main action but leaves 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%, and all three parameters have enums and German descriptions. The description mentions floor and equipment permissions but adds no format, constraint, or interpretation beyond the schema, and it does not mention the 'damage' parameter at all.

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 states a specific action ('Freigabe ... abgleichen' / 'Check ... permissions') and names both resources: floor and wet-cleaner permissions. This is substantively distinct from siblings such as saugwischer_reinigungsmittel_freigabe, but the description does not explicitly name an alternative to route against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before use' gives clear timing context: this check should be run before active wet cleaning. It does not state when not to use the tool, prerequisites such as manufacturer documentation, or which sibling to use instead for other approval checks.

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