Skip to main content
Glama

getecoback-raumklima

stromtarif_verbrauchsschwelle

Read-only

Verbrauchsschwelle zwischen niedrigem Grundpreis und niedrigem Arbeitspreis bestimmen. — Find the annual usage where two flat tariffs break even.

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": {
      "arbeit_a": "<arbeit_a>",
      "grund_a": "<grund_a>",
      "arbeit_b": "<arbeit_b>",
      "grund_b": "<grund_b>"
    },
    "name": "stromtarif_verbrauchsschwelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
grund_aYesGrundpreis A in Euro pro Jahr.
grund_bYesGrundpreis B in Euro pro Jahr.
arbeit_aYesArbeitspreis A als Brutto-€/kWh.
arbeit_bYesArbeitspreis B als Brutto-€/kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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, making it clear this is a safe, closed-domain computation, so the description is not the sole carrier of behavior. However, it adds nothing about the result: it does not say whether the output is kWh/year, what happens when one tariff dominates at every consumption level, or that there is no break-even in that case.

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 short and front-loads the purpose, with the English sentence making the German label unambiguous. The German and English sentences largely restate each other, which is mild redundancy rather than 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?

For a four-parameter calculation tool with fully documented inputs, the definition covers the inputs but leaves the output side underspecified. Since there is no output schema, the description should say what value comes back (annual kWh threshold) and how a no-break-even case is reported, which it does not.

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 carries a clear German unit description (€/year for Grundpreis, gross €/kWh for Arbeitspreis), so the schema does the heavy lifting. The description merely frames the two parameter pairs as the two tariffs to compare and adds no format or edge-case meaning beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific computation: the annual usage at which two flat tariffs break even, with the German framing of a threshold between a low base price and a low unit price. That is a distinct verb-plus-result, and no sibling in the catalog performs a tariff break-even calculation, so confusion is unlikely.

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: an agent can infer this is for comparing two tariff structures (base price A/B vs. unit price A/B), but the description never states when to pick this over another approach or what inputs are inappropriate. For a pure calculator the implied scope is probably enough, but no explicit when/when-not guidance is given.

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