Skip to main content
Glama

getecoback-raumklima

wohnmobil_nachwinter_befund_neu_oder_wiederholt

Read-only

Unterscheide neue von bereits dokumentierten Feuchtebefunden an denselben markierten Fahrzeugstellen — Separate new sightings from repeated findings after winter

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": {
      "alt_befunde": "<alt_befunde>",
      "neu_befunde": "<neu_befunde>",
      "gleiche_punkte": "<gleiche_punkte>",
      "alt_nicht_wieder_pruefbar": "<alt_nicht_wieder_pruefbar>",
      "gleiche_bezeichnungen": "<gleiche_bezeichnungen>"
    },
    "name": "wohnmobil_nachwinter_befund_neu_oder_wiederholt"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_befundeYesAnzahl markierter Stellen mit alter Beobachtung
neu_befundeYesAnzahl markierter Stellen mit Feuchtebefund in der erneuten Begehung
gleiche_punkteYesDavon mit Befund in beiden Protokollen an identischer Stelle
gleiche_bezeichnungenYesOrtscodes bezeichnen nachweislich dieselben Stellen und Beobachtungsmerkmale
alt_nicht_wieder_pruefbarYesWeitere alte Befundstellen ohne aktuelle Sichtprüfung

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 safety and scope profile is covered, and the description's 'Unterscheide' is consistent with a pure read/compute operation. Beyond that it adds little: with no output schema, an agent still cannot tell whether the result is counts, a per-location breakdown, or a verdict, nor how the 'nicht wieder prüfbar' remainder is reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence in German with an English gloss — the distinguishing verb is front-loaded and nothing is redundant. Size is well matched to a narrow five-parameter computation.

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?

All five parameters are required and fully documented in the schema, and the closed-world read-only annotations set expectations. The main gap is the return value: with no output schema and no description of the result shape, the definition is only just sufficient for a comparison tool whose whole purpose is to produce a new-vs-repeat split.

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 each of the five parameters carries its own German explanation, so the schema does the heavy lifting. The description adds only the overall framing of the comparison and no syntax, constraint, or relationship details (e.g. that 'gleiche_punkte' must be a subset of 'neu_befunde') beyond what the schema states.

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 gives a specific verb ('Unterscheide' / 'Separate') and a precise object (new vs. already-documented moisture findings at the same marked vehicle locations), which tells an agent this is a classification/comparison operation rather than a data fetch. It does not, however, contrast itself with any of the many similarly-named wohnmobil siblings, so sibling disambiguation is left to inference.

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 only implied: the phrase 'after winter' signals the post-winter re-inspection context in which this comparison applies. There is no explicit when-not guidance, no mention of prerequisites (e.g. that both an old and a new protocol must exist), and no reference to alternative tools for related tasks.

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