Skip to main content
Glama

getecoback-climate-weather

haushaltsstrom_abwesenheit_normalisieren

Read-only

Grundlast abziehen und Mehrverbrauch pro Anwesenheitstag zweier Wohnphasen vergleichen — Separate a measured background load from occupancy-day 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": {
      "a_tage": "<a_tage>",
      "b_tage": "<b_tage>",
      "a_anwesend": "<a_anwesend>",
      "b_anwesend": "<b_anwesend>",
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "abwesenheit_kwh_tag": "<abwesenheit_kwh_tag>"
    },
    "name": "haushaltsstrom_abwesenheit_normalisieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene kWh in der ersten Phase.
b_kwhYesGemessene kWh in der zweiten Phase.
a_tageYesKalendertage in der ersten Phase.
b_tageYesKalendertage in der zweiten Phase.
a_anwesendYesAnwesenheitstage in der ersten Phase.
b_anwesendYesAnwesenheitstage in der zweiten Phase.
abwesenheit_kwh_tagYesGemessene Grundlast pro Abwesenheitstag als eigene Annahme für beide Phasen.

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 the agent knows this is a safe, closed calculation with no side effects. The description adds the modeling assumption that a single measured background load is applied to both phases, which is genuinely useful context. It does not disclose the shape of the result (one number per phase, a delta, etc.) or how the calculation behaves when occupancy days 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with the operational core first, plus a short bilingual gloss. Nothing is redundant, though the German/English duplication is repetitive rather than informative.

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 seven-required-parameter computation with no output schema, the description covers the model but not the result. It never says what is returned or how ties, zero-occupancy phases, or unit conventions are handled, which matters for a tool whose entire value is a derived comparison.

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% and every parameter is described in the schema, so the baseline is 3. The description contributes interpretive meaning by explaining that abwesenheit_kwh_tag is a shared assumption subtracted from both phases and that the residual is expressed per occupancy day, which clarifies the relationship among the day, presence, and kWh parameters.

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 (subtract background load, compare excess consumption per occupancy day across two living phases) and identifies the resource as two phases of household electricity data. It is clearly more than a restatement of the tool name. It does not, however, distinguish itself from the sibling haushaltsstrom_geteilte_nutzung_szenario, which an agent would have to compare on its own.

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 explicit statement of when to use this tool versus another, and no named alternative. The intended scenario (two phases with measured totals plus absent-day counts) is implied by the description's framing, but an agent must infer it from the parameter set rather than from guidance.

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