Skip to main content
Glama

getecoback-raumklima

saugroboter_stationsbundle_abgleichen

Read-only

Roboter und separat etikettierte Station gegen das dokumentierte Bundle prüfen — Verify a robot vacuum bundle using robot and dock identifiers.

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": {
      "roboter": "<roboter>",
      "station": "<station>"
    },
    "name": "saugroboter_stationsbundle_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
roboterYesModellnummer vom Roboter.
stationYesSeparates Stationskennzeichen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the useful framing that the station is labeled separately from the robot and that the comparison target is a documented bundle, but it says nothing about what a mismatch or an 'unbekannt' value does to the outcome.

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 short sentence, front-loaded with the verb and the two inputs, with no filler. The bilingual duplication is slightly redundant but keeps the definition terse overall.

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?

For a two-parameter read-only lookup with full enum coverage and no output schema, the essentials are present. What is missing is the meaning of the result and the handling of the catch-all enum values, which matters because there is no output schema to explain the verdict.

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 both parameters are closed enums, so the schema already carries the parameter semantics. The description's only addition is clarifying that the station identifier is a separate label, which is marginal beyond what the schema fields state.

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 concrete verb (prüfen/verify) and a concrete resource (the documented bundle of robot vacuum plus separately labeled station), which separates it from siblings such as saugroboter_station_aufstellcheck. It is clear what is being checked, but it never states what the check produces or why the bundle is authoritative.

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 no when-to-use guidance: no mention of prerequisites, of when to prefer this over the other saugroboter_* tools, or of what to do when the identifiers are unknown. The phrase 'gegen das dokumentierte Bundle' implies a comparison baseline but leaves the selection condition to inference.

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