Skip to main content
Glama

getecoback-raumklima

stromkosten_fixanteil_gleicher_zeitraum

Read-only

Fixe Kosten und veränderliche Zusatzposten aus zwei bezahlten Strommonaten abgrenzen — Compare the fixed-cost burden at different measured monthly 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_cent": "<a_cent>",
      "b_cent": "<b_cent>",
      "fix_cent": "<fix_cent>",
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "basis_gleich": "<basis_gleich>"
    },
    "name": "stromkosten_fixanteil_gleicher_zeitraum"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene kWh A.
b_kwhYesGemessene kWh B.
a_centYesGesamtkosten A in Cent, einschließlich des gemeinsamen Fixbetrags.
b_centYesGesamtkosten B in Cent, einschließlich des gemeinsamen Fixbetrags.
fix_centYesBelegter in beiden Zeiträumen identischer Fixbetrag in Cent.
basis_gleichYesGleiche Dauer und gleiche Kostenabgrenzung ohne Sonderposten geprüft?

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?

The readOnlyHint/openWorldHint annotations already establish that this is a safe, self-contained computation, so the bar is lower. The description adds useful behavioral context — that the fixed amount must be identical in both periods and that variable items are separated out — but says nothing about what happens when the periods are not comparable (the basis_gleich=false case) or what the result contains.

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 efficient sentence pair with the core operation front-loaded; the German clause plus short English gloss is compact. The bilingual duplication is mildly redundant but not wasteful enough to hurt readability.

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 computation with no output schema, the description should at least indicate what is returned (fixed share, variable rate, per-month split). It conveys the input model well but leaves the result shape entirely unstated, which is the main gap.

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 every parameter (a_cent, b_cent, fix_cent, a_kwh, b_kwh, basis_gleich) is already documented with units and constraints. The description only restates the conceptual model of a shared fixed amount across two months and adds no format or edge-case detail 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 names a concrete operation — separating fixed costs from variable add-on items across two paid electricity billing months — and adds the comparison angle (fixed-cost burden at different measured usage). That is specific enough to identify the tool's job, though it does not name or contrast any sibling such as stromkosten_preis_und_menge_abgleichen.

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 when-to-use or when-not-to-use guidance and no alternative tool is mentioned. The only implicit cue is 'aus zwei bezahlten Strommonaten', which hints that two bills are required, but an agent gets no routing logic for choosing this over sibling cost tools.

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