Skip to main content
Glama

getecoback-raumklima

roboter_stationskontakt_und_sensor_pflegemethode

Read-only

Verhindere die Übertragung einer feuchten Kontaktpflege auf optische Flächen oder ein anderes Gerät — Separate documented care media for contacts and sensor windows

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": {
      "modell": "<modell>",
      "stelle": "<stelle>",
      "flaeche_und_modell_belegt": "<flaeche_und_modell_belegt>"
    },
    "name": "roboter_stationskontakt_und_sensor_pflegemethode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
stelleYesÄußerlich zugängliche Stelle im exakten Pflegebild
flaeche_und_modell_belegtYesDie Stelle wurde bei ausgeschaltetem Gerät und stromloser Station ohne Öffnen identifiziert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds a useful constraint — that care media for contacts and sensor windows must stay separate — but says nothing about what is returned, whether prior entries can conflict, or how the documented method is surfaced.

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?

Two short segments joined by an em dash, so there is little waste, but the imperative 'Verhindere…' reads as an instruction to the agent rather than a description of the tool, and the German and English halves partially duplicate each other.

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?

Three required parameters are fully documented in the schema and the read-only nature is annotated, so the basics are covered. However, for a tool whose purpose is to establish a documented care method, the description never says what the caller gets back or how the separation is enforced.

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 two parameters are enums, so the schema carries the parameter meaning. The description contributes nothing about 'modell', 'stelle', or 'flaeche_und_modell_belegt' beyond restating the contact-versus-sensor distinction implicitly.

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 frames the tool as a goal ('Verhindere die Übertragung einer feuchten Kontaktpflege auf optische Flächen') plus a phrase about 'separate documented care media', but never states a concrete verb such as 'record' or 'look up'. An agent can infer it concerns documenting the care method for a station contact versus a sensor window, but the actual operation is left implicit.

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 a thematic condition (wet contact care must not reach optical surfaces), but no explicit instruction on when to call this tool rather than a sibling, and no mention of preconditions beyond what the schema already enforces. The agent must guess the trigger.

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