Skip to main content
Glama

getecoback-raumklima

bodenpflege_sichtspuren_trockenprobe

Read-only

Nach dem Trocknen entfernte, verschobene und neu sichtbare Stellen getrennt zählen. — Separate cleared, spread and newly visible marks after a floor dries.

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": {
      "flecken_vorher": "<flecken_vorher>",
      "entfernt": "<entfernt>",
      "sichtbar_verschoben": "<sichtbar_verschoben>",
      "neue_stellen": "<neue_stellen>"
    },
    "name": "bodenpflege_sichtspuren_trockenprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
entferntYesMarkierte Stellen, die nach dem Trocknen sichtbar sauber erscheinen.
neue_stellenYesZusätzliche sichtbare Stellen außerhalb der ursprünglichen Markierungen.
flecken_vorherYesVor dem Wischen markierte Stellen.
sichtbar_verschobenYesAndere markierte Stellen, deren Spur verschoben oder verteilt erscheint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety is covered. The description adds the counting semantics of keeping three mark categories separate, but it says nothing about what is returned, whether counts are validated against flecken_vorher, or how totals are reported.

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 core instruction is front-loaded and short, but the same sentence is given in German and English, which duplicates content without adding meaning. The line is not bloated, but half of it is redundant.

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?

All four required parameters are documented in the schema, and read-only behavior is covered by annotations, so the definition is callable. However, for a counting tool with no output schema, it would help to describe what the tool returns or how counts are related to the prior marks.

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%, and each parameter is already documented with clear German descriptions and numeric bounds. The description reinforces the conceptual separation of categories but adds no format, constraint, or relationship detail beyond the schema.

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 counting action ('getrennt zählen') on a defined resource: cleared, displaced and newly visible marks after a floor dries. It is clear what the tool does, but it does not differentiate itself from sibling floor-care probes such as bodenpflege_referenzstellen_gegenprobe.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, and it names no alternative tool or prerequisite. The timing condition ('nach dem Trocknen') is implied by the task, but an agent receives no routing guidance.

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