Skip to main content
Glama

getecoback-climate-weather

saugroboter_umstellprobe_flaechengewinn

Read-only

Zusätzlich erreichte Bodenfläche nach einer einzigen Möbeländerung mit deren Aufwand vergleichen — Quantify newly cleaned floor area per minute of a reversible furniture move.

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": {
      "vorher_m2": "<vorher_m2>",
      "nachher_m2": "<nachher_m2>",
      "umstell_min": "<umstell_min>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "saugroboter_umstellprobe_flaechengewinn"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_m2YesNach dem Testlauf beobachtete gereinigte Fläche ohne Umstellen.
nachher_m2YesBeobachtete gereinigte Fläche mit derselben Einstellung nach einer Möbeländerung.
umstell_minYesGemessener gesamter Aufwand für Umstellen und Zurückstellen in Minuten.
vergleichbarYesGleicher Raum, Modus, übrige Hindernisse und ausreichend ähnlicher Testablauf?

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, so the agent knows this is a pure, side-effect-free local computation; the description correctly does not contradict that. What it adds beyond the annotations is only the 'reversible move' framing, which hints at safety expectations. It says nothing about how the result behaves when vergleichbar is false, whether a zero minute value is guarded, or what the returned figure looks like.

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 definition is a single front-loaded statement of the metric, with the German original immediately followed by an English rendering. It is short and wastes no words on filler. The bilingual duplication is somewhat redundant for a single agent, but it is brief and does not 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?

This is a small, purely computational tool with four required, fully documented scalar parameters, no nested structures, and no output schema, so the definition does not need to describe return values. The annotations carry the safety profile and the description carries the metric definition, which is sufficient to call it correctly. The only shortfall is the lack of guidance on the vergleichbar=false case.

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 documented in detail, making 3 the baseline. The description adds one genuinely useful piece of semantics by identifying the derived quantity as area per minute, which implicitly tells the agent that vorher_m2/nachher_m2 form the numerator and umstell_min the denominator. It does not explain how vergleichbar gates or invalidates the computed ratio, which is the one parameter with interpretive ambiguity.

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 concrete computation: comparing the extra cleaned floor area gained from a single reversible furniture move against the effort it costs, normalized per minute. The verb ('compare'/'quantify') and the resource (m² gained per minute of Umstell-Aufwand) are specific enough that an agent knows what kind of result to expect. It does not explicitly contrast itself with any sibling, which keeps it from a 5.

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?

Usage is implied rather than stated: it should be called after a test run with exactly one furniture change, since the metric is defined per single reversible move. There is no explicit when-not guidance (e.g. what to do when the move was not reversible or when several changes were made in one run) and no named alternative tool for that case.

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