Skip to main content
Glama

getecoback-raumklima

saugwischer_griffwechsel_routine

Read-only

Häufige Griffwechsel zweier Bedienabläufe anhand einer eigenen Proberunde vergleichen — Compare observed grip changes during two wet-cleaner control layouts.

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": {
      "wechsel_a": "<wechsel_a>",
      "wechsel_b": "<wechsel_b>",
      "runden_woche": "<runden_woche>",
      "gleiche_aufgabe": "<gleiche_aufgabe>"
    },
    "name": "saugwischer_griffwechsel_routine"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechsel_aYesGriffwechsel bei Ablauf A in einer vergleichbaren vollständigen Nutzung.
wechsel_bYesGriffwechsel bei Ablauf B in derselben Aufgabe.
runden_wocheYesGeplante vergleichbare Runden pro Woche.
gleiche_aufgabeYesWar derselbe Bedienablauf vollständig berücksichtigt, etwa Start, Modi und Stopp?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that the comparison is based on an observed trial round, but it does not explain how 'häufige Griffwechsel' are determined, what the comparison returns, or how to interpret the result.

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?

The definition is short and front-loads the purpose. The bilingual repetition is slightly redundant but not harmful, and every clause contributes to identifying the comparison being performed.

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 read-only comparison tool with four fully documented parameters and no output schema, the definition covers the basic inputs. However, it leaves the return value and interpretation of the comparison unexplained, which matters for an agent deciding what to do with the result.

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%, so all four parameters are already well documented. The description reinforces the trial-round context but adds no syntax, units, or interpretation beyond what the schema provides, so the baseline of 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 uses a specific verb ('vergleichen'/'Compare') and a clear resource: observed grip changes between two wet-cleaner control layouts. An agent can understand what is being compared, though there is no explicit differentiation from the many sibling saugwischer tools.

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 'anhand einer eigenen Proberunde' implies the tool is for comparing two control layouts from one's own trial run, but it does not state when to use this instead of related tools, nor does it give exclusions or prerequisites beyond the trial-round context.

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