Skip to main content
Glama

getecoback-raumklima

lichterkette_timer_netto

Read-only

Lichterketten-Zeitplan inklusive Dauerverbrauch des Timers vergleichen — Check net lighting savings after accounting for timer overhead.

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": {
      "watts": "<watts>",
      "hours": "<hours>",
      "newhours": "<newhours>",
      "days": "<days>",
      "timer": "<timer>",
      "price": "<price>"
    },
    "name": "lichterkette_timer_netto"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesNutzungstage, an denen der Timer steckt.
hoursYesBisherige Leuchtdauer pro Tag in Stunden.
priceYesArbeitspreis in EUR/kWh.
timerYesEigenverbrauch des Timers in W.
wattsYesGesamtleistung der Lichterkette in W.
newhoursYesGeplante Leuchtdauer pro Tag in Stunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 is covered. The description adds the substantive behavioral fact that the result is NET of the timer's standby draw, which is meaningful. It says nothing about what the output looks like (savings in EUR vs kWh), but for a pure read-only calculator that is a modest gap.

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?

One compact sentence pair with the key qualifier ('after accounting for timer overhead') front-loaded in the English half. The German/English duplication is slightly redundant but the definition is not padded with filler.

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 six-required-parameter calculator with no output schema, the description establishes the concept but not the result form — no indication whether it returns currency, kWh, or a comparison pair, nor how the 'old vs new hours' delta is expressed. Adequate to select the tool, thin for interpreting its output.

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%, so all six parameters (watts, hours, newhours, days, timer, price) are documented with units and ranges in the schema. The description adds no parameter-level meaning beyond that, so the 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 description names a specific computation — net lighting savings after subtracting the timer's own consumption — with a verb ('vergleichen'/'Check') and a resource ('Lichterketten-Zeitplan', 'timer overhead'). It is understandable what the tool computes, though the German phrasing 'Zeitplan ... vergleichen' is oblique and the English sentence is what actually conveys the purpose.

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?

No guidance on when to use this versus any sibling, no prerequisites, no exclusions. The only implicit cue is that it is a savings/overhead calculation, which overlaps conceptually with sibling energy-cost tools but the definition does not say so.

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