Skip to main content
Glama

getecoback-raumklima

saugwischer_reinigungsmittel_freigabe

Read-only

Reinigungsmittel und Dosierung mit Freigaben von Gerät und Boden abgleichen — Check approved cleaning solution and dilution for the exact equipment and surface.

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": {
      "equipment": "<equipment>",
      "surface": "<surface>",
      "dose": "<dose>"
    },
    "name": "saugwischer_reinigungsmittel_freigabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
doseYesVorgeschriebene Dosierung und Vorgehen eindeutig dokumentiert?
surfaceYesErlaubt der Bodenhersteller das Mittel für diese Oberfläche?
equipmentYesErlaubt die genaue Geräteanleitung dieses Mittel für den Tank?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety profile is covered. The description adds that the tool cross-checks approvals across equipment and surface rather than performing an action, which is useful behavioral context. However, it never says what the check produces, which matters for a verdict-style tool.

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 front-loaded sentence, which is good, but it is effectively written twice (German then English translation) with no extra information in the English half. The bilingual duplication consumes space without adding meaning for an agent.

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?

With three required enum inputs, no output schema, and no description of the return value, the agent cannot know what a verdict looks like or whether a 'no'/'unknown' combination changes the outcome. For a pure validation tool with no output schema, the description should explain the result it returns; that gap is significant.

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 of the three enum parameters has a precise German question, so the schema carries the parameter meaning. The description only loosely maps to them ('equipment', 'surface', 'dilution') and adds no syntax or interpretation guidance beyond the schema, matching the baseline 3.

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?

Uses a specific verb (abgleichen/check) plus a defined resource (cleaning agent and dosage against equipment and surface approvals), so an agent can tell it validates a cleaning-solution clearance. It falls short of 5 because the description mentions 'dilution' as if it were an input value, while the actual dose parameter only records whether dosage is documented — a small but real ambiguity.

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 when-to-use or when-not-to-use guidance is given; nothing distinguishes this from siblings such as saugwischer_bodenfreigabe, which appears to cover the floor-approval subset. The 'for the exact equipment and surface' phrasing implies it applies to a concrete device/surface combination, but the agent must infer that.

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