Skip to main content
Glama

getecoback-raumklima

saugroboter_station_raumwechsel_servicezugang_plan

Read-only

Vergleiche zwei Stationsplätze anhand der im Alltag wirklich benötigten Serviceöffnungen — Compare two docking locations for retained service access

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": {
      "gebraucht": "<gebraucht>",
      "a_oben": "<a_oben>",
      "a_vorne": "<a_vorne>",
      "b_oben": "<b_oben>",
      "b_vorne": "<b_vorne>"
    },
    "name": "saugroboter_station_raumwechsel_servicezugang_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_obenYesLässt sich die obere Klappe oder der benötigte Tank in Raum A vollständig bedienen?
b_obenYesLässt sich die obere Klappe oder der benötigte Tank in Raum B vollständig bedienen?
a_vorneYesIst der notwendige Zugang von vorne in Raum A frei?
b_vorneYesIst der notwendige Zugang von vorne in Raum B frei?
gebrauchtYesAm exakten Stationsmodell im Alltag benötigter Zugang

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds that the evaluation is deliberately restricted to access types actually needed in daily use, which is meaningful behavioral context. It does not disclose what the comparison yields (a verdict, a ranking, a tie-break rule), which is the main behavioral unknown.

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 bilingual sentence with the comparison criterion front-loaded and no filler. The German/English pairing is slightly redundant but cheap, and nothing in the sentence is wasted.

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?

There is no output schema, so the description carries the burden of telling the agent what a comparison returns — a recommendation, a boolean per room, or a scored verdict — and it does not. It also leaves open how mismatched requirements are handled, e.g., when only 'oben' is needed but only 'vorne' is free. For a decision tool with five required inputs, this is a notable omission.

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 each parameter already explains what the boolean means (top flap/tank operable, front access free) and what the 'gebraucht' enum selects. The description's framing of 'really needed' access reinforces the enum's role but adds no format or edge-case guidance beyond the schema. 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 verb and resource: compare two docking locations (Stationsplätze) on the criterion of everyday service access. That is clearly more informative than the tool name alone. It stops short of distinguishing itself from the similarly named sibling 'saugroboter_station_aufstellcheck', so an agent must infer which one fits its situation.

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?

The phrase 'im Alltag wirklich benötigten Serviceöffnungen' implies a practical siting decision, so the context of use is inferable. However, the description never states when to pick this over 'saugroboter_station_aufstellcheck' or what preconditions apply (e.g., that both rooms must already be candidate locations). Usage is implied rather than stated.

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