Skip to main content
Glama

getecoback-climate-weather

geraetetakt_aus_messung

Read-only

Aus dem Energiezähler effektive Laufzeit eines Geräts mit zwei stabilen Leistungsstufen abschätzen. — Infer the operating time of a two-state appliance from measured energy.

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": {
      "energie_kwh": "<energie_kwh>",
      "stunden": "<stunden>",
      "ruhe_w": "<ruhe_w>",
      "betrieb_w": "<betrieb_w>"
    },
    "name": "geraetetakt_aus_messung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruhe_wYesKonstante gemessene Wirkleistung in Ruhe in Watt.
stundenYesDauer des Beobachtungsfensters in Stunden.
betrieb_wYesKonstante gemessene Wirkleistung im Betrieb in Watt.
energie_kwhYesIm Beobachtungsfenster gemessene kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety and external-access behavior are covered. The description adds that the result is an estimate and assumes two stable power levels, which is useful, but it does not discuss accuracy, edge cases, or output units.

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 definition is short and front-loaded, with the German statement followed by an English equivalent. The bilingual duplication is minor redundancy but not enough to obscure the core purpose.

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 four-parameter calculation tool, the inputs are fully documented by the schema and safety is covered by annotations. However, there is no output schema and the description does not state the returned runtime's unit/format or edge-case behavior, leaving a modest completeness gap.

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?

All four parameters have 100% schema description coverage, including units and ranges. The description only restates the two-power-level/energy model conceptually and adds no syntax, unit, or constraint details beyond the schema.

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

Purpose5/5

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

The description gives a precise verb ('abschätzen'/'infer') and resource ('effektive Laufzeit eines Geräts'), plus the qualifying conditions 'two stable power levels' and 'from measured energy'. That scope is specific enough to separate it from general heater/energy siblings, even though no sibling is named.

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?

It implicitly defines the applicable context—two-state appliance with measured energy—but gives no explicit when-to-use/when-not guidance or named alternative. An agent can infer the use case, but routing guidance is only moderate.

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