Skip to main content
Glama

getecoback-climate-weather

geraeteverbrauch_nutzungsveraenderung

Read-only

Unterschied zwischen mehr Nutzung und anderem Verbrauch pro Vorgang rechnerisch aufteilen — Decompose an observed energy change into a usage-count effect and a per-task effect.

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_anzahl": "<vorher_anzahl>",
      "nachher_anzahl": "<nachher_anzahl>",
      "vorher_kwh_pro_vorgang": "<vorher_kwh_pro_vorgang>",
      "nachher_kwh_pro_vorgang": "<nachher_kwh_pro_vorgang>"
    },
    "name": "geraeteverbrauch_nutzungsveraenderung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_anzahlYesVollständige Vorgänge im ersten Beobachtungszeitraum.
nachher_anzahlYesVollständige Vorgänge in einem gleich langen zweiten Zeitraum.
vorher_kwh_pro_vorgangYesGemessener Mittelwert pro Vorgang vorher, in kWh.
nachher_kwh_pro_vorgangYesGemessener Mittelwert pro Vorgang nachher, in kWh.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, closed-world, non-mutating nature is established without the description. The description adds that the result is split along two causal dimensions, which is genuine context. However, with no output schema it never says what the decomposition actually returns (a pair of contributions? signed? in kWh?) or what sign convention applies when consumption falls.

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?

Two compact clauses, one per language, with the operative verb and the two resulting effects front-loaded ahead of any elaboration. There is no filler. The bilingual duplication costs some length but improves disambiguation, so it does not read as waste.

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?

For a pure computation tool the only value delivered is its return value, and there is no output schema and no description of the return shape, units, or sign handling. The parameter side is fully covered by the schema, but the result side is completely unaddressed. That leaves a real gap in what an agent needs in order to use the answer correctly.

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 parameter carries a precise German description with units and bounds, so the schema carries the semantics fully. The description adds nothing about the parameters beyond restating the concepts of usage count and per-task consumption. 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 German sentence names a specific operation (rechnerisch aufteilen) on a specific quantity (an observed energy change) into two named effects, and the English clause repeats it precisely. An agent knows this is an additive decomposition of a consumption delta, not a measurement or estimation tool. It does not distinguish itself against any other tool, but none of the sibling names suggest a competing decomposition function.

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?

Usage is only implied by the required parameter set: before/after counts plus before/after per-task kWh. There is no explicit statement of when to prefer this over a plain delta or a per-unit comparison, and no exclusions or preconditions are given. An agent can infer the situation, but must do the work itself.

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