Skip to main content
Glama

getecoback-climate-weather

saugwischer_uebergabe_bodenabschnitt_freigaben

Read-only

Ermittle, für wie viel der Zielraumfläche die alte Wischfreigabe noch belegt ist — Determine which floor area is still covered by the retained washing approval

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": {
      "zielraum_m2": "<zielraum_m2>",
      "bestaetigter_belag_m2": "<bestaetigter_belag_m2>",
      "ungeeignet_m2": "<ungeeignet_m2>",
      "gleiche_methode": "<gleiche_methode>"
    },
    "name": "saugwischer_uebergabe_bodenabschnitt_freigaben"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielraum_m2YesGesamte Zielraumfläche in m²
ungeeignet_m2YesZusätzliche ausdrücklich ausgeschlossene Teilfläche
gleiche_methodeYesGleiches Gerät, gleiche Wischmethode und gegebenenfalls gleiche freigegebene Lösung
bestaetigter_belag_m2YesTeilfläche, die eindeutig derselben freigegebenen Belagsausführung und Pflegeanweisung zugeordnet ist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 bar is lower. The description implies a read-only computation whose result is an area quantity, but it does not say whether the answer is an m² figure, a percentage, or a boolean, and no output schema exists to fill that gap. Nothing contradicts the annotations.

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 front-loaded sentence that states the computation before any detail. The bilingual duplication is arguably redundant, though it does aid parsing, and there is no filler beyond that.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a quantitative computation with four required numeric/boolean inputs and no output schema, so the description must explain the derivation rule and the shape of the answer. Instead it only restates the goal, leaving the agent unable to predict what a call will return or how unsuitable_m2 and gleiche_methode affect it.

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 every parameter carries its own German explanation, so the baseline of 3 applies. The description adds nothing about how the four inputs combine — in particular what gleiche_methode=true changes in the result — which is the one piece of semantics only the description could supply.

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 description names a verb ('Ermittle'/'Determine') and a resource ('which floor area is still covered by the retained washing approval'), so it is not a tautology. However, 'alte Wischfreigabe noch belegt' is dense domain jargon and the boundary against siblings such as saugwischer_bodenfreigabe or saugwischer_freigegebene_abschnitte_flaechenbilanz is never drawn. An agent can guess it computes a residual area but not confidently what kind of quantity it returns.

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?

There is no statement of when to call this versus the many adjacent saugwischer approval tools. No prerequisites, no exclusion conditions, and no alternative named. The agent must infer the call context entirely from the name.

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