Skip to main content
Glama

getecoback-raumklima

saugroboter_absaugstation_beutelkontrolle

Read-only

Beutelfüllung und leeren Roboterbehälter nach dem Absaugen unterscheiden — Decide whether to inspect the bag or log an incomplete auto-empty.

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": {
      "beutelsignal": "<beutelsignal>",
      "behaelter_leer": "<behaelter_leer>",
      "absaugung_bestaetigt": "<absaugung_bestaetigt>"
    },
    "name": "saugroboter_absaugstation_beutelkontrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
beutelsignalYesBeobachtung an der Station oder laut Anleitung.
behaelter_leerYesStaubbehälter im Roboter nach dem Lauf augenscheinlich leer?
absaugung_bestaetigtYesVollständiger Absaugvorgang laut Anzeige oder eigener Beobachtung bestätigt?

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. The description adds the two possible outcomes (inspect the bag vs. log an incomplete auto-empty), but it never states which input combination maps to which outcome, which is the core behavior of a decision tool. Note also a mild tension: 'log an incomplete auto-empty' sounds like a write, while annotations claim read-only.

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?

Two short clauses with the situation stated first and the decision second; nothing extraneous. The German and English halves restate each other somewhat, but it remains tight and front-loaded.

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?

No output schema exists, so the description must carry the decision semantics — yet the mapping from the three required inputs to the two outcomes is left entirely unstated. For a diagnostic decision tool with fully required parameters, that is a meaningful gap, though all inputs themselves are documented.

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%, with each of the three parameters (bag signal enum, container empty, suction confirmed) already documented in the schema. The description does not add format, precedence, or interpretation rules beyond what the parameters say, so it lands at the baseline.

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 the specific resource (bag fill level and the robot's dust container after auto-empty) and states the action: distinguishing the two situations and deciding between inspecting the bag or logging an incomplete auto-empty. It is far more specific than the tool name alone, though the phrase 'unterscheiden — decide' is slightly abstract about what the tool actually returns.

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 timing is implied by 'nach dem Absaugen' (after the auto-empty), which tells the agent this is a post-run check. However, there is no explicit when-not guidance and no routing to related siblings such as the dust-bag usage plan or station setup check, so the agent must infer the boundary itself.

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