Skip to main content
Glama

getecoback-raumklima

saugwischer_vortrieb_arbeitsrichtung_beleg

Read-only

Prüfe, ob Vortrieb die benötigte Arbeitsrichtung am Boden abdeckt — Check whether floor washer assistance covers the required direction

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": {
      "modell": "<modell>",
      "vorgang": "<vorgang>",
      "angebot_variante_bestaetigt": "<angebot_variante_bestaetigt>"
    },
    "name": "saugwischer_vortrieb_arbeitsrichtung_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaue Variante laut Angebot
vorgangYesGesuchte Unterstützung
angebot_variante_bestaetigtYesVollständige Modellbezeichnung mit Anleitung abgeglichen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered without help. The description adds nothing behavioral beyond that: it does not say what the check returns, what happens with 'anderes', or what the confirmation flag gates. With annotations carrying the safety profile, this contribution is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short and front-loaded with the verb, but it is a bilingual duplication where the English half repeats the German half without adding information. Every sentence earns its place only once; the second rendering is padding.

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 small three-parameter read-only check with full schema coverage and annotations, the description is adequate to identify the tool. However, since no output schema exists, the description should explain what the verification returns (boolean verdict? evidence record?), 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% with two enums fully described, so the schema does the heavy lifting and the baseline of 3 applies. The description never mentions modell, vorgang, or angebot_variante_bestaetigt, so it adds no meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does supply a verb ('Prüfe/Check') and a subject ('Vortrieb ... Arbeitsrichtung am Boden'), so the agent learns this is a yes/no coverage check for floor-washer drive direction. However, the English gloss 'floor washer assistance' is a loose rendering of 'Vortrieb', and the sentence largely restates the tool name in two languages rather than pinning down the exact decision being made. It offers no differentiation from the many saugwischer_* siblings.

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 statement of when to call this versus the surrounding saugwischer tools, no prerequisites beyond the schema's own flag, and no exclusions. The agent must infer the triggering situation entirely from the tool name and the enum values.

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