Skip to main content
Glama

getecoback-climate-weather

heizmeldung_raumabdeckung_zusammenfassen

Read-only

Geprüfte und ungeprüfte Räume in einer Heizungsmeldung auseinanderhalten — Summarize coverage of a heating-fault report across rooms.

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": {
      "relevante_raeume": "<relevante_raeume>",
      "zeitgleich_gemessen": "<zeitgleich_gemessen>",
      "ziel_unterschritten": "<ziel_unterschritten>",
      "warmwasser_beobachtung": "<warmwasser_beobachtung>"
    },
    "name": "heizmeldung_raumabdeckung_zusammenfassen"
  }
}

Input Schema

NameRequiredDescriptionDefault
relevante_raeumeYesRäume, für die die Meldung gelten soll.
zeitgleich_gemessenYesRäume mit Messung im gleichen Beobachtungsfenster.
ziel_unterschrittenYesUnter den gemessenen Räumen unter dem jeweiligen Zielwert.
warmwasser_beobachtungYesBeobachteter Warmwasserzustand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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 known. The description adds only a garbled hint about distinguishing checked vs unchecked rooms and says nothing about how coverage is computed, how the warm-water observation affects the result, or what the summary contains — thin for a computation tool with 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.

Conciseness3/5

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

It is short, but the German clause duplicates the English one while being garbled and less clear, so it adds noise rather than front-loading value. A single clean sentence stating purpose plus when to use it would earn the space better.

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 tool is a simple read-only aggregation with fully documented parameters, so the bar is modest. Still, with no output schema the description should say roughly what the summarized coverage looks like, and it does not — an agent knows the topic but not the shape of the answer.

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%, with all four parameters (including the warm-water enum) documented in the schema itself. The description adds no meaning beyond that — no relationship between relevante_raeume and zeitgleich_gemessen, no note that ziel_unterschritten is a subset of measured rooms. Baseline 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?

The English half gives a specific verb plus resource: 'Summarize coverage of a heating-fault report across rooms', so an agent can tell this is an aggregation/coverage tool rather than a measurement tool. It does not explicitly differentiate itself from the sibling heizmeldung_sollwertzeit_messbezug, and the German half is garbled enough to be unreadable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no prerequisite, and no named alternative. The only hint at scope is 'Geprüfte und ungeprüfte Räume ... auseinanderhalten', which suggests it is for separating verified from unverified rooms but never states the condition under which an agent should pick this over the messbezug sibling.

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