Skip to main content
Glama

getecoback-climate-weather

strombudget_verbrauch_messspanne

Read-only

Ein kWh-Limit gegen die gemeinsame Messunsicherheit zweier getrennter Verbrauchsgruppen bewerten — Decide whether a budget is certainly met, exceeded, or unresolved under two measurement bounds.

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_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "a_fehler_kwh": "<a_fehler_kwh>",
      "b_fehler_kwh": "<b_fehler_kwh>",
      "budget_kwh": "<budget_kwh>"
    },
    "name": "strombudget_verbrauch_messspanne"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesGemessene kWh der ersten Gruppe über den gesamten Budgetzeitraum.
b_kwhYesGemessene kWh der zweiten Gruppe im selben Zeitraum, ohne Überlappung.
budget_kwhYesKWh-Limit für diese beiden Gruppen in diesem Zeitraum.
a_fehler_kwhYesMaximale absolute Messabweichung der ersten Gruppe in kWh.
b_fehler_kwhYesMaximale absolute Messabweichung der zweiten Gruppe in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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. The description adds genuine value beyond that by disclosing the output logic: the answer is one of three states, including an explicit 'unresolved' case when the measurement bounds straddle the budget — a behavior an agent could not infer from the annotations.

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

Conciseness5/5

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

A single front-loaded sentence naming the computation, followed by the decision outcome; no filler, no restatement of the schema.

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?

With no output schema, the description usefully compensates by enumerating the three possible verdicts. The only residual gap is the aggregation rule for the two error terms, which matters for interpreting 'unresolved' results but does not block correct invocation given a fully described 5-parameter schema.

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%, so all five parameters are already documented with units and ranges. The description adds only the framing that the two errors form a 'gemeinsame Messunsicherheit' and that the groups are non-overlapping, without specifying how the bounds combine (sum vs. other aggregation), so the 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?

States a specific verb ('bewerten'/decide) plus the exact resource: a kWh budget judged against the combined measurement uncertainty of two separate consumption groups. The three-way verdict (certainly met / exceeded / unresolved) further pins down what the tool computes, distinguishing it from simpler budget-bound siblings, though it never names an alternative.

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 implied by the stated decision problem — use it when a budget must be judged despite measurement error across two groups — but there is no explicit when-not guidance and no routing to siblings such as strombudget_verbrauchsgrenze or strombudget_hitzetage_reserve.

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