Skip to main content
Glama

getecoback-climate-weather

saugwischer_treppentransport_touren

Read-only

Tragewege eines Saugwischers zwischen Abstellort, Stockwerken und Pflegestelle erfassen — Count one-way transfers between floors for a wet-cleaning plan.

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": {
      "von_station": "<von_station>",
      "zwischen_zonen": "<zwischen_zonen>",
      "zur_pflege": "<zur_pflege>",
      "antrieb_vorhanden": "<antrieb_vorhanden>"
    },
    "name": "saugwischer_treppentransport_touren"
  }
}

Input Schema

NameRequiredDescriptionDefault
zur_pflegeYesTreppenübergänge zur Pflegestelle und danach zum Abstellort, ohne Doppelzählung.
von_stationYesEinzelne notwendige Treppenübergänge vom Abstellort bis zur ersten Zone.
zwischen_zonenYesTreppenübergänge zwischen zu reinigenden Zonen.
antrieb_vorhandenYesDas Gerät hat Vortrieb auf dem Boden?

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 does not contradict it. The description adds only that transfers are counted one-way across three location types, which is modest context beyond the annotations; it says nothing about validation, caps at 100, or what the tool computes or returns.

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?

It is short, but the German sentence and the English sentence are largely restatements of each other rather than complementary information. The English half also says only "between floors," dropping the storage-location and care-station endpoints present in the German, so the duplication loses precision instead of reinforcing it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-required-parameter, no-output-schema counting tool with read-only annotations, the definition is adequate: the agent knows the domain and the counting unit. What it omits — whether the result is a total, per-leg counts, or a validated constraint — is a genuine gap but a limited one given the fully documented schema.

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 baseline is 3. The description's mention of Abstellort, Stockwerken, and Pflegestelle loosely maps to von_station, zwischen_zonen, and zur_pflege, but it adds no counting rules or units beyond what the schema already states, including the no-double-counting rule.

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 ("erfassen" / "count") and a concrete resource (one-way stair transfers of a wet-cleaning vacuum between storage location, floors, and care station), so an agent can tell this is a transfer-counting tool rather than a cleaning-area or sequence tool. It stops short of naming any sibling, so differentiation is by subject matter only.

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?

"for a wet-cleaning plan" hints at the planning context in which this belongs, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many saugwischer_* siblings. The agent must infer that this is the counting step that precedes planning 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