Skip to main content
Glama

getecoback-raumklima

strommessung_messluecke_spannweite

Read-only

Auswirkung einer Strommesslücke als bedingte Unter- und Obergrenze berechnen — Bound unobserved energy using a defensible power ceiling instead of filling a gap with an average.

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": {
      "beobachtet_kwh": "<beobachtet_kwh>",
      "luecke_min": "<luecke_min>",
      "obergrenze_w": "<obergrenze_w>",
      "obergrenze_belegt": "<obergrenze_belegt>"
    },
    "name": "strommessung_messluecke_spannweite"
  }
}

Input Schema

NameRequiredDescriptionDefault
luecke_minYesLänge aller zusammengezählten Messlücken, in Minuten.
obergrenze_wYesNachvollziehbar begründete Obergrenze der Wirkleistung in der Lücke, in W.
beobachtet_kwhYesGemessene Verbrauchsenergie aller lückenlosen Abschnitte, in kWh.
obergrenze_belegtYesIst die Obergrenze für genau diese Lücke begründbar?

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, so safety is covered. The description adds that the result is a bound conditioned on a defensible ceiling, but it never says what happens when obergrenze_belegt is false (error, refusal, or null bound) nor what the returned quantities look like.

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?

One front-loaded sentence stating effect, method, and the alternative it rejects. The bilingual restatement is slightly redundant but functions as a gloss rather than filler.

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 small read-only computation with four fully documented required parameters this is close to sufficient, but with no output schema the description should indicate that the result is a pair of energy bounds in kWh and how the boolean gate affects it.

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 detail, including units and ranges. The description only reinforces the notion of a 'defensible' ceiling, which maps loosely to obergrenze_belegt without adding format or semantics beyond the schema.

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?

Pairs a specific verb (berechnen/bound) with a specific resource (unobserved energy from a measurement gap) and adds the method signature — conditional lower and upper bounds rather than a point estimate. This implicitly separates it from the extrapolation sibling, but no sibling is named outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'instead of filling a gap with an average' gives a clear selection condition: use this when a conservative bound is wanted rather than an imputed mean. It stops short of naming an alternative tool or stating when-not to use it.

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