Skip to main content
Glama

getecoback-raumklima

arbeitszimmer_abwaerme_vergleich

Read-only

Interne Wärmequellen anhand gemessener elektrischer Leistung vergleichen — Estimate the indoor heat reduction between two measured office-device configurations.

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": {
      "vorher_w": "<vorher_w>",
      "nachher_w": "<nachher_w>",
      "energie_bleibt_im_raum": "<energie_bleibt_im_raum>"
    },
    "name": "arbeitszimmer_abwaerme_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_wYesGemessene Gesamtleistung der Geräte am Arbeitsplatz vor der Umstellung in Watt.
nachher_wYesGemessene Gesamtleistung bei vergleichbarer Arbeit nach der Umstellung in Watt.
energie_bleibt_im_raumYesDie eingesetzte elektrische Energie bleibt im betrachteten Raum, z. B. kein nennenswerter Akkuaufbau oder Außenabluft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safe, local, non-mutating nature is known. The description adds that the output is an 'Estimate' derived from measured power, which is useful, but it does not disclose the underlying assumption (electrical energy fully converting to room heat) or what the returned quantity looks like, given there is 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 and front-loaded, but the German clause and the English clause restate essentially the same scope rather than complementing each other, which is mild padding. The key differentiator (comparison of two configurations) is nevertheless in the leading position.

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 three-parameter, purely computational read-only tool this is adequate on the input side, and annotations cover the safety profile. However, with no output schema the description should tell the agent what result is produced (a watt difference? a temperature delta?), which it does not.

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%: vorher_w, nachher_w and energie_bleibt_im_raum are each documented in the schema with units, bounds and the physical caveat. The description adds no semantics beyond what the schema supplies, 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?

The description names a specific verb (compare) plus a resource (interne Wärmequellen / measured electrical power) and states the intended result (indoor heat reduction between two configurations). This clearly distinguishes it from measurement-only siblings, though it never names a neighbouring tool such as heizwaerme_arbeitsplatz or geraetewechsel_rechnen to sharpen the boundary.

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 'between two measured office-device configurations' implies the use case (a before/after device swap with measured wattage) but there is no explicit when-to-use, when-not-to-use, or prerequisite statement. An agent must infer the scenario from the parameter intent rather than being told it.

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