Skip to main content
Glama

getecoback-raumklima

ventilator_wochenbudget_nachtmix

Read-only

Aus zwei gemessenen Nachtprofilen berechnen, wie viele intensivere Nächte in dein Wochenbudget passen — Allocate stronger fan nights while reserving the measured baseline for every night.

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": {
      "naechte": "<naechte>",
      "ruhige_nacht_kwh": "<ruhige_nacht_kwh>",
      "starke_nacht_kwh": "<starke_nacht_kwh>",
      "budget_kwh": "<budget_kwh>"
    },
    "name": "ventilator_wochenbudget_nachtmix"
  }
}

Input Schema

NameRequiredDescriptionDefault
naechteYesAnzahl der betroffenen Nächte.
budget_kwhYesEigenes Energie-Budget für alle Nächte. In kWh.
ruhige_nacht_kwhYesGemessene Energie für das sparsamere, persönlich ausreichende Lüfterprofil. In kWh.
starke_nacht_kwhYesGemessene Energie für das intensivere Lüfterprofil. In kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the allocation rule — reserve the measured baseline for every night and spend the remainder on stronger nights — which is genuine behavioral context, but it omits what happens when the budget is insufficient, whether the result is rounded down, and there is no output schema explaining the return.

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?

A single sentence front-loads the computation, which is good, but it is expressed twice (German then English) with slightly different framing, adding length without new information. The em-dash clause repeats the reservation idea rather than sharpening it.

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-required-parameter computation with no output schema, the description should at minimum say what is returned and how rounding or budget shortfall is handled. It covers the intent and the reservation constraint but leaves the result shape ambiguous.

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 coverage is 100%, so each parameter is already documented with units and bounds. The description clarifies the relationship between the two profile values (baseline is kept every night, the stronger profile is the discretionary one), which adds a little meaning beyond the schema but no arithmetic or input-validation details.

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?

States a concrete operation: from two measured night profiles, compute how many stronger nights fit in a weekly energy budget. The verb and resource are identifiable, but the actual result (a count of strong nights? a kWh remainder?) is only implied by 'wie viele intensivere Nächte', not stated.

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 indication of when to prefer this over siblings such as ventilator_stufenwahl_tastendruecke or the noise-compromise tool, and no prerequisites or exclusions. Usage is only inferable from the word 'Wochenbudget'.

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