Skip to main content
Glama

getecoback-raumklima

saugwischer_randstreifen_flaeche

Read-only

Übrig bleibenden Randstreifen an ausgewählten Wänden abschätzen — Estimate additional manual edge coverage after a wet-cleaner 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": {
      "straight_edge_m": "<straight_edge_m>",
      "gap_mm": "<gap_mm>"
    },
    "name": "saugwischer_randstreifen_flaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
gap_mmYesIn der vorgesehenen Fahrtrichtung gemessener ungereinigter Randstreifen.
straight_edge_mYesGesamtlänge der zu prüfenden geraden Wandstücke, ohne doppelt gezählte Strecken.

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 the safety profile is covered externally. The description adds that the result is an estimate of residual manual edge work, but says nothing about assumptions, units of the returned value, or how the two inputs combine.

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 with the operative concept first and no filler. The bilingual duplication is mildly redundant but does not obscure the meaning.

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?

For a pure read-only estimation tool with no output schema, the description should clarify what is returned (area, length, or time) and in which units. Inputs are fully documented, but the output side is left entirely unspecified, which is a real gap given there is no output schema to fall back on.

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 coverage is 100% and both parameters carry detailed German descriptions including bounds (0–300) and measurement conditions (measured in travel direction, no double counting). The description adds no parameter-level meaning beyond that, so the schema-only baseline of 3 applies.

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?

States a specific verb (abschätzen/estimate) and a specific resource (remaining edge strip / additional manual edge coverage after a wet-cleaner pass), which tells an agent exactly what is computed. It does not name or contrast any sibling tool, so differentiation must be inferred from the context wording alone.

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 phrase 'after a wet-cleaner pass' implies the situation in which the tool applies, but there is no explicit when-to-use rule, no exclusions, and no pointer to alternative tools for related estimates. An agent must guess whether this or a sibling area tool is appropriate.

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