Skip to main content
Glama

getecoback-climate-weather

stromgruppe_arbeitspreis_stufe_zusatzauftrag

Read-only

Zusatzkosten zweier Aufgaben an einer belegten Mengenstufe abhängig von ihrer Reihenfolge aufschlüsseln — Attribute marginal task costs across a documented progressive usage threshold.

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": {
      "freie_menge_erster_stufe_kwh": "<freie_menge_erster_stufe_kwh>",
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "stufe_eins_cent": "<stufe_eins_cent>",
      "stufe_zwei_cent": "<stufe_zwei_cent>"
    },
    "name": "stromgruppe_arbeitspreis_stufe_zusatzauftrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene zusätzliche Energiemenge für A.
b_kwhYesGemessene zusätzliche Energiemenge für B.
stufe_eins_centYesPreis der verbleibenden ersten Stufe in Cent/kWh.
stufe_zwei_centYesPreis nur weiterer kWh ab der Grenze in Cent/kWh.
freie_menge_erster_stufe_kwhYesIm Zeitraum verbleibende Menge bis zur belegten Preisstufe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety profile is covered and the description only needs to add computational context. It does add some: the operation is a marginal-cost attribution across a progressive threshold rather than a simple sum, and the order of the two tasks matters. However it never states what order assumption is used, whether both orders are reported, or what the result looks like — the key behavioral facts for a calculation tool are left implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, the scoping statement front-loaded, which is good. But the English half is a near-verbatim mirror of the German with no new information, so a full sentence does not earn its place. The density of domain jargon ('belegte Mengenstufe', 'Zusatzauftrag') also costs more parsing effort than it returns.

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 five-required-parameter pure calculation with no output schema, the agent ideally needs to know the return shape (per-task marginal amounts, totals, ordering of the breakdown). The description gestures at cost attribution but never specifies it, and the order-dependence claim remains unexplained. Combined with complete schema coverage, this is adequate but leaves a real gap for a numeric compute tool.

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_kwh, b_kwh, stufe_eins_cent, stufe_zwei_cent, freie_menge_erster_stufe_kwh) is already documented in the schema. The description reinforces the two-tier progressive model ('belegte Mengenstufe', 'documented progressive usage threshold') but adds no syntax, unit, or per-parameter meaning beyond that. 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 concrete verb ('aufschlüsseln'/'attribute') and a concrete resource: the marginal costs of two tasks (A and B) at an already-consumed quantity tier. That is more specific than the tool name alone and an agent can tell it apart from sibling 'stromgruppe_*' tools that deal with budgets, caps, or completeness discounts. It stops short of 5 because the pivotal qualifier 'abhängig von ihrer Reihenfolge' is never resolved — no order input exists in the schema, so the agent cannot tell whether one order is assumed or both are computed.

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 when-to-use, when-not-to-use, or alternative-naming content anywhere in the description. The many closely named 'stromgruppe_*' siblings make routing genuinely ambiguous, and nothing here helps the agent choose. Usage must be inferred entirely from the tool name and parameter set.

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