Skip to main content
Glama

getecoback-raumklima

haushaltsstrom_geteilte_nutzung_szenario

Read-only

Getrennt gemessene Verbräuche und gemeinsame Stromkosten nach eigenen Schlüsseln aufteilen — Build a private two-party household cost-sharing scenario from direct and shared usage.

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_eigen_kwh": "<a_eigen_kwh>",
      "b_eigen_kwh": "<b_eigen_kwh>",
      "gemeinsam_kwh": "<gemeinsam_kwh>",
      "preis_eur_kwh": "<preis_eur_kwh>",
      "fix_eur": "<fix_eur>",
      "a_gemeinsam_prozent": "<a_gemeinsam_prozent>",
      "a_fix_prozent": "<a_fix_prozent>"
    },
    "name": "haushaltsstrom_geteilte_nutzung_szenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
fix_eurYesFestkosten desselben Zeitraums.
a_eigen_kwhYesNur Person A zugeordneter Verbrauch im Zeitraum.
b_eigen_kwhYesNur Person B zugeordneter Verbrauch im Zeitraum.
a_fix_prozentYesAbgesprochener prozentualer Anteil von A an den Fixkosten.
gemeinsam_kwhYesGetrennt gemessener gemeinsamer Verbrauch ohne die beiden Einzelposten.
preis_eur_kwhYesGeplanter einheitlicher Arbeitspreis für alle drei Verbrauchsmengen.
a_gemeinsam_prozentYesAbgesprochener prozentualer Anteil von A am gemeinsamen Verbrauch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 closed-world pure computation. The description reinforces that it is a scenario builder, but says nothing about what the result contains, how rounding or the uniform price assumption is handled, or that negative prices are accepted.

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?

A single compact sentence, front-loaded with the German statement of the operation. The English half restates the same content for bilingual coverage rather than adding new information, which is mild redundancy but not bloat.

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?

All seven required parameters are schema-documented, so the agent can call the tool, but with no output schema the description should say something about the returned breakdown (per-person shares of shared and fixed costs). That gap leaves the agent guessing at the result shape.

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 seven parameters are already documented in detail. The description's 'nach eigenen Schlüsseln aufteilen' loosely corresponds to the two percentage parameters but adds no format, unit, or interaction guidance beyond the schema.

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 gives a specific verb and resource: splitting separately measured consumption and shared electricity costs by agreed keys to build a two-party household cost-sharing scenario. That is far more concrete than the name alone, though it never distinguishes itself from the similarly-named sibling scenario calculators (e.g. stromtarif_teilgarantie_szenario).

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 phrase 'private two-party household', which scopes the audience but not the triggering condition. There is no statement of when to choose this over the other scenario tools, nor any prerequisite or exclusion.

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