Skip to main content
Glama

getecoback-climate-weather

saugroboter_station_aufstellcheck

Read-only

Freien Anfahr- und Bedienraum einer Roboterstation prüfen — Compare free approach and service space with the station 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": {
      "front_mm": "<front_mm>",
      "left_mm": "<left_mm>",
      "right_mm": "<right_mm>",
      "min_front_mm": "<min_front_mm>",
      "min_side_mm": "<min_side_mm>",
      "tanks_accessible": "<tanks_accessible>"
    },
    "name": "saugroboter_station_aufstellcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
left_mmYesFreier Abstand links neben der Station.
front_mmYesFreie Tiefe vor dem Gehäuse.
right_mmYesFreier Abstand rechts neben der Station.
min_side_mmYesGeforderter Freiraum je Seite laut Anleitung. Bei unterschiedlichen Vorgaben den größeren Wert angeben.
min_front_mmYesGeforderter Freiraum vor der Station laut Anleitung.
tanks_accessibleYesDeckel, Beutel und gegebenenfalls beide Tanks lassen sich vollständig bedienen?

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 safety profile is covered and the description only needs to add context. It adds that the comparison is against manual specifications, which frames the operation as a pure evaluation rather than a measurement. However, it never says what the check produces (per-side pass/fail vs. a single verdict) or whether tanks_accessible overrides numeric results.

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 the action first and the comparison target second. The German and English halves are near-duplicates, which is mild redundancy, but the total length is small and nothing important is buried.

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?

Six required parameters are fully documented in the schema and the operation is read-only, so the core is covered. With no output schema, though, the description should have said what the result looks like — whether each clearance is reported individually, how tanks_accessible factors in, and what a failure verdict means — and it does not.

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%, including units, the 0–3000 mm bounds, and the instruction to use the larger value when side requirements differ, so the schema carries the parameter burden. The description itself contributes no additional parameter meaning beyond 'approach and service space' and 'station manual', which map loosely onto front/side and min_* fields.

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?

States a specific verb and resource: 'Freien Anfahr- und Bedienraum einer Roboterstation prüfen' — checking free approach and service clearance around a robot station. The English half adds that it compares against the station manual. It does not name or distinguish itself from any sibling, so it stops short of a 5.

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 only implied: an agent can infer you call this when you have measured clearances and the manual's required values. There is no explicit when-to-use or when-not-to-use statement and no mention of alternatives such as measuring thresholds or furniture passage with the sibling tools.

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