Skip to main content
Glama

getecoback-climate-weather

klima_service_modus_laufabgleich

Read-only

Zwei bereits notierte Klimageräteläufe nach Modus und Zieltemperatur gegenüberstellen — Identify whether a reported mode or setpoint was changed between observed runs.

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": {
      "normaler_modus": "<normaler_modus>",
      "auffaelliger_modus": "<auffaelliger_modus>",
      "soll_vorher_c": "<soll_vorher_c>",
      "soll_nachher_c": "<soll_nachher_c>",
      "sollwerte_belegt": "<sollwerte_belegt>"
    },
    "name": "klima_service_modus_laufabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
soll_vorher_cYesNotierter Sollwert des Referenzlaufs in °C.
normaler_modusYesModus während des früheren Referenzlaufs.
soll_nachher_cYesNotierter Sollwert des gemeldeten Laufs in °C.
sollwerte_belegtYesBeide Sollwerte zur jeweiligen Zeit dokumentiert?
auffaelliger_modusYesModus während des späteren beobachteten Laufs.

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 profile is covered. The description adds that the tool operates purely on two recorded runs and that documented setpoints matter ('sollwerte_belegt'), but it does not say what happens with undocumented values or what the comparison result looks like.

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 short sentences, front-loaded with the comparison and then the diagnostic question it answers. The bilingual duplication is mildly redundant but serves as a clarifying gloss rather than filler.

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?

With five required parameters and no output schema, the description should ideally indicate the shape or meaning of the comparison verdict, and it does not. It covers the inputs and the question being answered adequately for a read-only check, but leaves the result semantics implicit.

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 description coverage is 100% and every parameter carries its own German description and, for the two mode fields, an enum, so the schema does the heavy lifting. The description corroborates the two compared dimensions (mode and target temperature), which is a small but consistent addition beyond the schema; baseline would be 3.

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 verb and resource: comparing two already-recorded AC runs by mode and target temperature to detect a changed mode or setpoint. It is specific enough that an agent understands the operation without opening the schema, though it does not explicitly differentiate itself from the many neighbouring klima_* diagnostic 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 'bereits notierte' runs implies the tool applies only to retrospective, already-observed data rather than live device queries, which is useful implied guidance. However, there is no explicit statement of when to use this versus alternatives, no exclusions, and no prerequisites.

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