Skip to main content
Glama

getecoback-climate-weather

ventilator_uebergabe_markierte_stufenpaare

Read-only

Prüfe, ob eine veraltete Stufenmarkierung einer anderen Steuerungsart entspricht — Compare marked fan settings by actual control mode after handoff

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": {
      "alte_markierung": "<alte_markierung>",
      "neuer_modus": "<neuer_modus>",
      "alte_stufe": "<alte_stufe>",
      "neue_stufe": "<neue_stufe>",
      "bedienteil_unveraendert": "<bedienteil_unveraendert>"
    },
    "name": "ventilator_uebergabe_markierte_stufenpaare"
  }
}

Input Schema

NameRequiredDescriptionDefault
alte_stufeYesStufennummer, nur bei fester Stufe relevant
neue_stufeYesAm Ziel abgelesene Stufennummer
neuer_modusYesAm neuen Standort beobachteter Modus
alte_markierungYesBedeutung der alten Markierung laut Protokoll
bedienteil_unveraendertYesDerselbe Ventilator mit identischem Bedienteil

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 readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a cross-check of an old marking against an actually observed mode, which is useful context, but it does not say what the tool returns on match vs. mismatch or whether any record is altered.

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?

Two compact clauses with the core condition front-loaded; no wasted preamble. The bilingual restatement is mildly redundant but genuinely helps disambiguate the German terminology.

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 described, and annotations cover read-only safety. However, with no output schema the agent cannot tell whether a successful call yields a boolean match, a discrepancy description, or an empty acknowledgment — a meaningful gap for a comparison/verification tool.

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, including both enums, is documented in the schema itself. The description adds no parameter-level meaning beyond what is already structured, so the 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 and resource: check whether an outdated stage marking ("veraltete Stufenmarkierung") corresponds to a different control mode, i.e. compare marked fan settings by actual control mode after a handoff. That is concrete enough to distinguish it from generic stage-selection siblings, but the description never names a related tool or clarifies what the comparison result means.

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 only usage cue is the trailing "after handoff" phrase, which implies the temporal context in which the check applies. There is no explicit when-to-use vs. when-not guidance and no alternative tool is offered for the case where the marking is current rather than outdated.

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