Skip to main content
Glama

getecoback-raumklima

strombudget_restwochenpfad

Read-only

Ein laufendes Monatslimit nach Zwischensaldo auf verbleibende Werktage und Wochenendtage umlegen — Find the remaining workday allowance after actual usage and planned weekend loads.

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": {
      "budget_kwh": "<budget_kwh>",
      "bisher_kwh": "<bisher_kwh>",
      "werktage_offen": "<werktage_offen>",
      "wochenendtage_offen": "<wochenendtage_offen>",
      "wochenendtag_kwh": "<wochenendtag_kwh>"
    },
    "name": "strombudget_restwochenpfad"
  }
}

Input Schema

NameRequiredDescriptionDefault
bisher_kwhYesSchon gemessener Monatsverbrauch in kWh.
budget_kwhYesEigenes Monatslimit in kWh.
werktage_offenYesVerbleibende Werktage.
wochenendtag_kwhYesGeplanter Verbrauch je solchem Tag in kWh.
wochenendtage_offenYesVerbleibende Wochenendtage beziehungsweise Tage mit höherem Bedarf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered and the bar is lower. The description sketches the computation order (residual after actual usage, planned weekend loads, spread over remaining days), which adds some behavioral insight, but it omits rounding, unit handling, and behavior when open-day counts are zero.

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?

It is a single sentence, but it is stated twice, once in German and once in English, and the two versions are not equivalent — the English drops the 'umlegen' allocation idea. The duplicated bilingual phrasing spends space without adding information.

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?

Five required parameters and no output schema, so the description carries the burden of saying what comes back. 'Remaining workday allowance' hints at a per-workday figure but never states whether one number or a per-day path is returned, nor how weekend days are accounted for in the result.

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 the baseline is 3 and the schema already explains every parameter. The description adds framing by implying how 'bisher_kwh' becomes an interim balance and how the weekend parameters feed the allocation, but gives no formula or sign conventions beyond that.

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 operation on a specific resource: re-allocating a running monthly limit, after an interim balance, across remaining weekdays and weekend days. An agent can tell this is a budget-splitting calculator rather than a measurement or comparison tool. It does not, however, distinguish itself explicitly from the nearby strombudget_* siblings.

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?

There is no when-to-use guidance, no preconditions (e.g. that the month must still be running), and no mention of an alternative sibling. The agent must infer the invocation context purely from the parameter names.

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