Skip to main content
Glama

getecoback-raumklima

strombudget_verbrauchsgrenze

Read-only

Aus Monatsbudget und Tarif ein jährliches Verbrauchslimit ableiten. — Turn a monthly electricity budget into a maximum annual consumption target.

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": {
      "monatsbudget_eur": "<monatsbudget_eur>",
      "grund_eur_jahr": "<grund_eur_jahr>",
      "arbeit": "<arbeit>",
      "geplant_kwh_jahr": "<geplant_kwh_jahr>"
    },
    "name": "strombudget_verbrauchsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeitYesBrutto-Arbeitspreis in €/kWh.
grund_eur_jahrYesFeste jährliche Tarifkosten in Euro.
geplant_kwh_jahrYesAktuell erwarteter Jahresverbrauch in kWh.
monatsbudget_eurYesDurchschnittlich vorgesehenes Monatsbudget in Euro.

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 and openWorldHint annotations already tell the agent this is a pure, offline, side-effect-free computation, so the description need not re-establish safety. It adds the useful fact that the delivered value is a maximum annual consumption figure, but it never explicitly names the output unit (kWh/year) or confirms that the result is a deterministic derived number, and there is no output schema to carry that.

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?

Two compact sentences with the derivation front-loaded and no filler or hedging. The only inefficiency is that the German and English renderings are literal duplicates rather than complementary information, so one of them is purely redundant for a monolingual reader.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a small deterministic four-parameter calculation with fully documented inputs, so completeness demands are modest. The description conveys the conceptual inputs and the nature of the result; the one real gap is that, absent an output schema, it does not pin down the return value's unit or format, which would matter for chaining results into other tools.

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%, with every one of the four parameters carrying units and min/max bounds, so the schema does the heavy lifting. The description mentions only budget and tariff generically and adds no syntax, unit, or interpretation detail beyond what the schema already provides, which is the correct baseline for full schema coverage.

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 states a concrete verb and result: deriving an annual consumption limit from a monthly budget and a tariff. That is specific enough for an agent to know exactly what the tool computes, though it never contrasts itself with any sibling tool, so it stops short of full sibling differentiation.

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 guidance about when to use this versus alternatives, no preconditions stated beyond the implicit inputs, and no mention of what to do if the caller already has a consumption figure or wants the inverse calculation. The purpose sentence implies a use case but never states one.

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