Skip to main content
Glama

getecoback-climate-weather

saugwischer_selbstreinigung_restpflicht_lesen

Read-only

Ermittle verbleibende manuelle Pflichtschritte trotz Selbstreinigungsmodus — Find manual steps still documented for a self-cleaning floor washer

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>",
      "pflegebereich": "<pflegebereich>"
    },
    "name": "saugwischer_selbstreinigung_restpflicht_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaue Modellvariante mit passender Anleitung
pflegebereichYesZu prüfender manueller Arbeitsschritt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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, covering the safety profile. The description adds that it reports still-documented manual steps, which is useful nuance, but does not describe output format, limitations, or any caveats beyond that.

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 description is a single front-loaded sentence with the key concept first. The bilingual repetition is redundant but does not make it verbose enough to obscure the purpose.

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 simple read-only lookup with two fully documented enum parameters and clear annotations, the description is sufficient. It could say more about the returned manual steps, but no output schema exists and the core behavior is clear.

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% for both enum parameters, so the schema already explains model variant and care area. The description adds no meaningful parameter-level detail beyond that structured documentation.

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?

States a specific verb ('Ermittle') and resource ('verbleibende manuelle Pflichtschritte trotz Selbstreinigungsmodus'), making the retrieval target clear. It does not explicitly contrast with sibling saugwischer tools, so it falls short of full sibling differentiation.

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 description implies usage when checking remaining manual work after a self-cleaning cycle, but gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. No prerequisites or exclusions are stated.

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