Skip to main content
Glama

getecoback-climate-weather

duschhalter_feldwechsel_bestandsbeobachtung_abgrenzen

Read-only

Vorhandene Beobachtung zu einer Halterstelle bei Wechsel von Fläche, Saugnapf oder Sichtzeit neu einordnen — Mark which parts of a prior contact observation do not carry over.

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": {
      "identischer_halter": "<identischer_halter>",
      "gleiche_kontaktstelle": "<gleiche_kontaktstelle>",
      "zustand_unveraendert": "<zustand_unveraendert>",
      "alte_notiz_datiert": "<alte_notiz_datiert>"
    },
    "name": "duschhalter_feldwechsel_bestandsbeobachtung_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
alte_notiz_datiertYesDer vorliegende Befund lässt sich einem konkreten Zeitpunkt zuordnen.
identischer_halterYesDasselbe Zubehör mit derselben Kontaktfläche wie im alten Eintrag.
zustand_unveraendertYesSeit der Beobachtung keine Änderung an Oberfläche oder Kontaktteil dokumentiert.
gleiche_kontaktstelleYesDieselbe Untergrundstelle und Kontaktlage sind bestätigt.

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?

Annotations already declare this as a read-only, non-open-world operation. The description adds the key behavioral context that it evaluates which parts of a prior observation do not carry over, but it does not describe the result format or how the four booleans determine the outcome.

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 definition is brief and front-loads the scenario in which the tool applies. The bilingual phrasing is slightly redundant, but there is no substantial wasted text.

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-boolean classification tool with no output schema, the description gives the scenario but leaves unclear what form the "marking" result takes. It is adequate because the schema fully documents the inputs, but it could better explain the operational 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?

Schema description coverage is 100%, so all four boolean parameters are already well documented in the input schema. The description adds no parameter-specific meaning beyond that structured documentation.

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 states a specific operation: reclassifying an existing observation of a holder location when the surface, suction cup, or observation time changes, and marking which parts no longer carry over. This is clearer than a tautology, but terms such as "Halterstelle" and "Sichtzeit" remain somewhat abstract.

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 description identifies the triggering situation (change of surface, suction cup, or observation time), which implies when the tool applies. It does not state when not to use the tool or name an alternative sibling, so guidance is present but incomplete.

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