Skip to main content
Glama

getecoback-raumklima

dreame_station_orange_weiss_signalzustand

Read-only

Ordne ein Stationslicht der tatsächlich beobachteten Dreame-Station und Signalart zu — Interpret a status light using the exact listed Dreame dock manual

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>",
      "signal": "<signal>",
      "standort_belegt": "<standort_belegt>"
    },
    "name": "dreame_station_orange_weiss_signalzustand"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
signalYesSignal an der Station, nicht am Roboter
standort_belegtYesLicht stammt eindeutig von der zum Modell dokumentierten Station

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 lookup. The description usefully adds that the answer must derive from the exact listed manual and the concretely observed station rather than free inference, but it says nothing about the shape or confidence of the resulting interpretation.

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 a bilingual gloss, which is efficient. The German/English duplication is mildly redundant but aids disambiguation for a German-titled tool.

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?

There is no output schema, so the description ideally would indicate what an 'interpretation' returns (e.g., a status meaning or a manual reference). It covers the input intent and closed-world constraint but leaves the return value underspecified for a three-parameter 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?

Schema coverage is 100% with three documented parameters and two enums, so the schema carries the parameter burden. The description adds no further detail about model names, signal vocabulary, or how 'standort_belegt' affects the outcome; 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?

The description names a specific action and resource: assign/interpret a station light ('Ordne ein Stationslicht ... zu', 'Interpret a status light'). It is clearly distinguishable from the sibling tools about tanks, docking ramps and water levels, though it does not explicitly name a contrasting alternative.

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?

Usage is implied rather than stated: 'der tatsächlich beobachteten Dreame-Station' and 'exact listed Dreame dock manual' suggest it should only be used for an actually observed dock signal matched against a listed model. There is no explicit when-not-to-use guidance, no mention of what to do for a signal on the robot itself (that constraint only appears in the schema), and no named alternative.

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