Skip to main content
Glama

getecoback-raumklima

saugwischer_geteilte_pflege_letzte_tankphase

Read-only

Prüfe, ob ein dokumentierter Tankpflegeschritt nach der letzten Nutzung in beiden Räumen stattfand — Check if floor washer tank care followed the latest use

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": {
      "raum_a_ende_min": "<raum_a_ende_min>",
      "raum_b_ende_min": "<raum_b_ende_min>",
      "tankpflege_min": "<tankpflege_min>",
      "tankpflege_nach_anleitung": "<tankpflege_nach_anleitung>"
    },
    "name": "saugwischer_geteilte_pflege_letzte_tankphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
tankpflege_minYesZeitpunkt der jüngsten dokumentierten Tankpflege
raum_a_ende_minYesEnde der letzten Nutzung in Raum A im gemeinsamen Protokoll
raum_b_ende_minYesEnde der letzten Nutzung in Raum B im selben Protokoll
tankpflege_nach_anleitungYesDokumentierter Schritt betrifft den Schmutzwassertank nach der genauen Geräteanleitung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 externally. The description adds the conceptual definition of the check (both rooms, after the latest use) but says nothing about the outcome, edge cases such as missing documentation, or how the two-room comparison is resolved.

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 front-loaded and short, but roughly half the text is a German/English restatement of the same sentence rather than new information. The structure is clean; the bilingual duplication does not fully earn its place.

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

Completeness2/5

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

With no output schema, the description carries the burden of explaining what a 'check' returns — a boolean verdict, a per-room result, or raised concerns. It does not, leaving the agent unable to predict the response for a four-parameter verification tool.

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, which establishes a baseline of 3. The description adds only a slight framing — that both room end times come from the same shared record and are compared against the tank-care timestamp — without clarifying units or tolerance.

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 specific verb ('Prüfe' / 'Check') and a concrete subject — whether a documented tank-care step occurred after the latest use in both rooms. An agent can tell this apart from the sibling pflege_* tools because it is scoped to floor-washer tank care across two rooms. It stops short of differentiating itself explicitly from any named alternative.

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 use this tool versus the many sibling Pflege tools, no prerequisites, and no exclusion condition. Usage must be inferred entirely from the topic wording, which is thin for a 32-sibling family.

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