Skip to main content
Glama

getecoback-raumklima

reinigungszonen_nach_moebelrueckkehr

Read-only

Vor dem Zurückstellen die berührte Bodenfläche und die noch abzutrocknenden Stellen abgleichen — Identify pending floor patches where staged furniture footprints would cover wet zones.

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": {
      "rueckstellflaeche_m2": "<rueckstellflaeche_m2>",
      "noch_feucht_unter_moebeln_m2": "<noch_feucht_unter_moebeln_m2>",
      "noch_feucht_ausserhalb_m2": "<noch_feucht_ausserhalb_m2>"
    },
    "name": "reinigungszonen_nach_moebelrueckkehr"
  }
}

Input Schema

NameRequiredDescriptionDefault
rueckstellflaeche_m2YesGesamte geplante Möbel-Standfläche.
noch_feucht_ausserhalb_m2YesNoch feuchte Fläche außerhalb der Möbel-Standfläche.
noch_feucht_unter_moebeln_m2YesDavon bei einer Sichtkontrolle noch erkennbar feucht.

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 nothing beyond that: it does not say what happens when the entered sub-areas exceed the total return area, whether out-of-range values are rejected, or what the agent should do with the result — all relevant for a comparison/validation calculation.

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 appropriately short and front-loads the situational context, but the German and English sentences restate each other with different framing rather than complementing one another, so half the text is largely redundant for a non-bilingual reader.

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 three-number computation with full schema documentation and no output schema, the definition is close to sufficient. The remaining gap is that it never indicates the shape of the answer (flagged patches, boolean, area delta), which the agent needs since no output schema exists.

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 the three area parameters are already documented in the schema and the baseline of 3 applies. The description's phrases 'berührte Bodenfläche' and 'noch abzutrocknende Stellen' only loosely gesture at the parameter set and add no interpretation rule beyond the schema.

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 English half names a recognizable operation — identifying pending floor patches where staged furniture would cover wet zones — but the verb 'Identify' combined with the preceding German sentence ('Bodenfläche ... abgleichen') leaves it ambiguous whether the tool reconciles areas, returns flagged zones, or just reports a conflict. No sibling tool is named or contrasted, so an agent cannot distinguish it from adjacent cleaning/drying tools by the description alone.

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?

'Vor dem Zurückstellen' implies a usage moment (before furniture is put back), which is genuine but thin guidance. There are no exclusions, no prerequisites, and no pointer to an alternative tool for any adjacent task such as measuring residual moisture or checking drying progress.

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