Skip to main content
Glama

getecoback-climate-weather

beleuchtung_schaltgruppen_belegung

Read-only

Strombedarf zweier separat schaltbarer Leuchtengruppen mit gemeinsamem und getrenntem Nutzungsanteil vergleichen — Estimate the benefit of separately switching two light groups during partly shared use.

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": {
      "a_w": "<a_w>",
      "b_w": "<b_w>",
      "nur_a_h": "<nur_a_h>",
      "nur_b_h": "<nur_b_h>",
      "beide_h": "<beide_h>"
    },
    "name": "beleuchtung_schaltgruppen_belegung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wYesGemessene Leistungsaufnahme Leuchtengruppe A in Watt.
b_wYesGemessene Leistungsaufnahme Leuchtengruppe B in Watt.
beide_hYesStunden, in denen beide Gruppen benötigt werden.
nur_a_hYesStunden, in denen nur Gruppe A benötigt wird.
nur_b_hYesStunden, in denen nur Gruppe B benötigt wird.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a comparison/estimation of shared versus separate usage, but it does not describe what the calculation returns, what assumptions it makes, or how the comparison is expressed.

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?

The description is front-loaded and compact: a German sentence followed by an English restatement. The bilingual repetition is slightly redundant, but it is not padded with irrelevant material.

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?

This is a simple read-only calculation with five fully documented parameters, so the definition is mostly adequate. However, without an output schema, the description should say more about what the comparison produces (for example, savings values or comparative totals) and any assumptions behind the estimate.

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 the five parameters are already clearly documented in the schema with units and ranges. The description adds conceptual context about two light groups with shared and separate usage, but no parameter-level meaning beyond what the schema already provides.

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 states a specific verb (compare / estimate) and resource (electricity demand of two separately switchable light groups), including the shared-versus-separate usage distinction. It is clear enough for an agent to understand the tool without opening the schema, though it does not name or distinguish any sibling tool.

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 purpose implies when the tool is useful: estimating the benefit of separately switching two light groups during partly shared use. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative for related calculations.

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