Skip to main content
Glama

getecoback-raumklima

saugroboter_sensorhinweis_pflege

Read-only

Sensorhinweis von sichtbar verschmutzter zugänglicher Stelle trennen — Pick a manual-approved sensor care or support step after an alert.

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": {
      "hinweis_erneut": "<hinweis_erneut>",
      "sichtbar_verschmutzt": "<sichtbar_verschmutzt>",
      "pflege_dokumentiert": "<pflege_dokumentiert>"
    },
    "name": "saugroboter_sensorhinweis_pflege"
  }
}

Input Schema

NameRequiredDescriptionDefault
hinweis_erneutYesDerselbe Sensorhinweis trat nach korrekter zugelassener Pflege erneut auf?
pflege_dokumentiertYesFür diese Sensorfläche liegt eine Pflegemethode in der genauen Herstelleranleitung vor?
sichtbar_verschmutztYesDie laut Anleitung zugängliche Sensorfläche ist sichtbar verschmutzt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 agent knows this is a safe, closed-world read/decision operation. The description adds the useful gate that only manual-approved care steps qualify, which goes beyond the annotations. It does not, however, disclose what the tool actually returns or how the three booleans combine into an outcome, leaving the core behavior opaque.

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?

Two short clauses with no filler, and the alert context is front-loaded. The bilingual em-dash construction makes the sentence feel like two unrelated fragments stitched together rather than one coherent statement, which costs a little clarity but not length.

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 no output schema and only boolean inputs, the description is the only place an agent can learn what the tool produces and how the three flags map to a care or support decision. It gestures at a selection but never states the result shape or the decision logic, leaving a substantial gap for a triage-style tool.

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 three parameters carry full German-language descriptions (100% schema coverage), so the schema already defines hinweis_erneut, sichtbar_verschmutzt and pflege_dokumentiert precisely. The description adds only the general framing of an alert-driven care decision and contributes no extra meaning about how these flags are evaluated together, so the baseline 3 applies.

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 a specific domain action (isolating a sensor alert caused by a visibly soiled, accessible sensor surface) and pairs it with an English gloss about choosing a manual-approved care or support step. However, the verb "trennen" is ambiguous and the two halves describe different things – a diagnostic separation and a step selection – so an agent cannot say with confidence whether the tool returns a decision, a step, or a confirmation. It is more specific than a tautology but does not cleanly separate itself from the many sibling saugroboter_* care tools.

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

Usage Guidelines3/5

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

"after an alert" gives a usable trigger condition, and "manual-approved" implies a prerequisite (a documented manufacturer care method must exist). There is no explicit when-not guidance, no named alternative among the sensor/care siblings, and no statement of what to do if the surface is not visibly dirty.

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