Skip to main content
Glama

getecoback-raumklima

stromeinsparung_rechnung_teilverbrauch_scope

Read-only

Eine behauptete Prozentersparnis an einem Gerät auf den dokumentierten Anteil der HaushaltskWh begrenzen — Translate a component energy claim to its maximum stated whole-use share.

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": {
      "haushalt_kwh": "<haushalt_kwh>",
      "teil_kwh": "<teil_kwh>",
      "einsparung_teil_prozent": "<einsparung_teil_prozent>",
      "gleiche_nutzung": "<gleiche_nutzung>"
    },
    "name": "stromeinsparung_rechnung_teilverbrauch_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
teil_kwhYesTatsächlich enthaltene kWh der betroffenen Anwendung.
haushalt_kwhYesGesamtstrom im identischen Zeitraum in kWh.
gleiche_nutzungYesSind Zeitfenster und gewünschte Leistung vergleichbar?
einsparung_teil_prozentYesBelegte relative Einsparung dieser Anwendung in Prozent.

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-world computation; the description adds the semantic that the result is a bounded maximum rather than a raw claim. However, it does not say what the tool does when inputs are contradictory (e.g. gleiche_nutzung=false) or what form the bounded result takes, which is the key behavioral unknown for a pure calculation.

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 core operation before the English restatement. The bilingual duplication is somewhat redundant, but as a translation aid for a German-named tool it does not materially bloat the text.

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?

With four required numeric/boolean parameters and no output schema, the description should explain the return value (a capped percentage? an absolute kWh figure?) and the failure mode for gleiche_nutzung=false. It covers the intent adequately but leaves these call-relevant details unstated.

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 four parameters are already documented in the schema with ranges and meaning. The description only echoes the concepts (percentage claim, household kWh, device share) without adding interpretation such as how teil_kwh relates to haushalt_kwh or what 'gleiche_nutzung' gates. Baseline 3 applies.

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 — capping a claimed percentage saving for one device to the documented share of household kWh — so the verb ('begrenzen'/'Translate') and resource are identifiable. It does not differentiate itself from any of the many sibling scope/calculation tools, and the dual German/English phrasing makes the core action slightly harder to pin down on first read.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The only hint of a precondition is the 'gleiche_nutzung' ('comparable time window and power') parameter, but the description never states what should happen when that condition fails, leaving the agent to infer usage rules.

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