Skip to main content
Glama

getecoback-climate-weather

saugwischer_akkuflaeche

Read-only

Aus einer eigenen Reinigungsprobe die Fläche pro nutzbarer Akkuladung abschätzen — Estimate wet-cleaning area per usable charge from a measured pass.

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": {
      "test_m2": "<test_m2>",
      "test_min": "<test_min>",
      "usable_min": "<usable_min>",
      "target_m2": "<target_m2>"
    },
    "name": "saugwischer_akkuflaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_m2YesVergleichbare Fläche des eigenen Probelaufs.
test_minYesGemessene Reinigungszeit für diese Fläche in Minuten.
target_m2YesZu reinigende Fläche innerhalb dieser Ladung.
usable_minYesBeim gleichen Modus gemessene nutzbare Reinigungsminuten je Ladung.

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 only needs to add computational context. It does confirm the tool is a pure derivation from user-supplied measurements, but it does not disclose how the estimate is formed (proportional scaling, capping, rounding) or whether target_m2 is validated against the estimate rather than just consumed.

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?

A single compact sentence that front-loads the input source and the estimated quantity. The German/English duplication is slightly redundant but serves bilingual readers and adds no real bloat.

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?

Four required numeric parameters and no output schema mean the description should ideally indicate what comes back (area per charge alone, or also whether target_m2 fits). It covers the input premise adequately but leaves the return value and the role of target_m2 ambiguous, which is a meaningful gap for a calculation 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%, with every parameter documented and bounded, so the baseline is 3. The description adds no extra meaning about units, plausible ranges, or how test_m2/test_min relate to usable_min and target_m2 beyond restating the general idea of a measured pass.

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?

Names a specific verb ('abschätzen' / 'estimate') and a specific derived quantity (wet-cleaning area per usable battery charge) derived from a user's own measured test pass. This distinguishes it from sibling computation tools such as saugwischer_mittelmenge or saugwischer_wasserbilanz, though it never explicitly contrasts itself with them.

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 phrase 'aus einer eigenen Reinigungsprobe' / 'from a measured pass' implies a precondition: you must already have measurement data from your own device run. However, there is no explicit when-to-use vs. when-not guidance and no named alternative for agents that lack measurement data or want a model-based estimate instead.

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