Skip to main content
Glama

getecoback-raumklima

waesche_umsetzen_wasserflecken_wegbefund

Read-only

Wasserflecken vor und nach zwei getrennten Transportabschnitten lokalisieren — Separate marks that appeared on a carry leg from marks present beforehand.

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": {
      "vor_start": "<vor_start>",
      "nach_a": "<nach_a>",
      "nach_b": "<nach_b>",
      "kein_zwischenwischen": "<kein_zwischenwischen>"
    },
    "name": "waesche_umsetzen_wasserflecken_wegbefund"
  }
}

Input Schema

NameRequiredDescriptionDefault
nach_aYesNach Abschnitt A dort kumuliert sichtbare Flecken.
nach_bYesNach Abschnitt B dort kumuliert sichtbare Flecken.
vor_startYesSchon vorher auf der abgegrenzten Route sichtbare Wasserflecken.
kein_zwischenwischenYesWurde auf derselben markierten Fläche ohne Zwischenwischen und andere dokumentierte Nutzung beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safe, closed-world read/computation. The description adds the idea that it compares marks across two legs, but says nothing about what is returned (counts, a difference, a verdict) or how the 'kein_zwischenwischen' gate affects the result, which is the behavioral core here.

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 short and front-loaded, but the sentence is stated twice in German and English with identical meaning, which is pure redundancy rather than added information. The dash-joined bilingual restatement makes it slightly harder to parse than a single clean statement.

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?

For a four-parameter read-only comparison tool with no output schema, the definition covers the input intent adequately but leaves the return value unaddressed. An agent calling it cannot predict whether it gets a boolean 'new marks appeared' verdict, a per-leg delta, or just an echo of the inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% — all four parameters have their own German descriptions with ranges — so the schema carries the load and a baseline of 3 applies. The description goes slightly beyond by explaining the conceptual split (before the start vs. after legs A and B), which clarifies why three separate counts are needed.

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 resource (Wasserflecken) and a specific operation (lokalisieren/separate marks from two transport legs versus marks present beforehand), so an agent can tell what is being computed. It stops short of 5 because the operation is framed as a measurement scenario rather than a clear action verb, and no sibling tool is named for contrast.

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?

Nothing states when this tool should be chosen over alternatives, nor any precondition or exclusion. The only implicit cue is the 'ohne Zwischenwischen' observation condition, which is really a parameter constraint rather than usage guidance.

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