Skip to main content
Glama

getecoback-raumklima

thermostat_kopfzuordnung_raumplan

Read-only

Eindeutige Bezeichnungen für mehrere Heizkörper im selben Zimmer planen — Count thermostat labels missing from a room with multiple radiator heads.

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": {
      "koepfe_im_raum": "<koepfe_im_raum>",
      "eindeutig_markiert": "<eindeutig_markiert>",
      "zimmername_eindeutig": "<zimmername_eindeutig>"
    },
    "name": "thermostat_kopfzuordnung_raumplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
koepfe_im_raumYesZahl der tatsächlich vorhandenen Thermostatköpfe im Raum.
eindeutig_markiertYesDavon vor Ort und im Verzeichnis eindeutig wiedererkennbare Köpfe.
zimmername_eindeutigYesIst der Name des Raums bei Übergaben eindeutig?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 covered. The description adds no behavioral context beyond that: it does not say whether the result is a computed shortfall, whether ambiguous room names alter the outcome, or what the caller receives. The two language versions even describe different behaviours, which muddies rather than clarifies.

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?

Two short sentences, but one is a German paraphrase and the other an English gloss of a different operation, so half the text is duplicated and partly conflicting rather than front-loaded with a single clear statement of purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place that could tell an agent what the tool returns; it does not. For a read-only computation whose value depends on how the three inputs are combined, this leaves an important gap that the schema and annotations cannot fill.

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 three parameters carries a clear German explanation, so the schema does the heavy lifting and a baseline 3 applies. The description adds nothing about how the parameters combine — notably that the useful value is likely koepfe_im_raum minus eindeutig_markiert, and how zimmername_eindeutig gates the result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The German half states a verb and resource ("Eindeutige Bezeichnungen ... planen" — plan unique labels for several radiators in one room), but the English half gives a different operation ("Count thermostat labels missing"). An agent can infer the domain (thermostat head labelling in a multi-radiator room) yet cannot be sure whether the tool returns a count, a naming plan, or both, and nothing distinguishes it from the many sibling thermostat_* tools.

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 statement of when to use this versus alternatives, no prerequisites, and no exclusion of cases (e.g. single-radiator rooms). The only implicit trigger is the phrase "room with multiple radiator heads", which is context rather than guidance.

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