Skip to main content
Glama

getecoback-raumklima

wohnmobil_standwinter_belueftung_vom_befund_trennen

Read-only

Unterscheide beim erneuten trockenen Sichtbefund ein zuvor geändertes Lüftungsmuster von erledigter Ursachenprüfung — Separate a cleared visual symptom from a resolved source in the camper

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": {
      "erste_stelle": "<erste_stelle>",
      "zweite_stelle": "<zweite_stelle>",
      "fachtuer_zustand_gewechselt": "<fachtuer_zustand_gewechselt>",
      "quelle_unabhaengig_geprueft": "<quelle_unabhaengig_geprueft>"
    },
    "name": "wohnmobil_standwinter_belueftung_vom_befund_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
erste_stelleYesZuerst beobachtetes Merkmal an der markierten Stelle
zweite_stelleYesSpätere Sichtkontrolle am selben markierten Punkt
fachtuer_zustand_gewechseltYesZwischen den Begehungen wurde die Fachtürstellung dokumentiert geändert
quelle_unabhaengig_geprueftYesMögliche weitere Feuchteursachen wurden separat durch die verantwortliche Person geprüft

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation already establishes that this is a safe, non-mutating operation, so the description does not need to repeat that. The description adds context about separating a visual symptom from a resolved source, but it does not explain what the tool returns or how the distinction is represented, which is a meaningful gap given there is no output schema.

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 description is a single front-loaded sentence and is not padded with unnecessary detail. The bilingual German-English repetition is somewhat dense, but it does not add significant waste and keeps the core distinction visible early.

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?

The schema fully documents the four required inputs, but the tool has no output schema and the description does not explain return values or the resulting distinction. For a read-only classification task with an abstract purpose, the definition is minimally adequate but leaves the agent without a clear picture of the observable outcome.

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?

The input schema has full description coverage for all four parameters, including enum values and boolean meanings. The description does not mention any parameter names or add meaning beyond the schema, so the schema carries the parameter explanation and the baseline score of 3 is appropriate.

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 names two states to distinguish: a cleared visual symptom and a resolved source, in the context of a repeated dry visual finding. It is clear enough to understand the tool's purpose, but it does not differentiate itself from the many similarly named sibling tools.

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?

The phrase 'beim erneuten trockenen Sichtbefund' implies the tool is used during a repeated dry visual inspection, which is a useful usage condition. However, there are no explicit when-to-use or when-not-to-use guidelines and no alternative tools are named.

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