Skip to main content
Glama

getecoback-raumklima

strommessung_gemeinsamer_offset_differenz

Read-only

Beim A/B-Vergleich belegten gemeinsamen additiven Messfehler von laufabhängigen Fehlern trennen — Bound a power difference with or without verified common-mode cancellation.

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_w": "<a_w>",
      "b_w": "<b_w>",
      "rest_a_w": "<rest_a_w>",
      "rest_b_w": "<rest_b_w>",
      "offset_grenze_w": "<offset_grenze_w>",
      "gleicher_offset_belegt": "<gleicher_offset_belegt>"
    },
    "name": "strommessung_gemeinsamer_offset_differenz"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_wYesGemessene Wirkleistung A in Watt.
b_wYesGemessene Wirkleistung B in Watt.
rest_a_wYesUnterschiedlicher laufabhängiger maximaler Fehler A in Watt.
rest_b_wYesUnterschiedlicher laufabhängiger maximaler Fehler B in Watt.
offset_grenze_wYesMaximaler additiver Offset je Messung in Watt.
gleicher_offset_belegtYesIst für beide Werte derselbe unveränderte additive Offset belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this a safe, read-only, closed-world computation, so the safety profile is covered. The description adds genuine behavioral context by indicating that the result depends on whether common-mode cancellation is verified (the gleicher_offset_belegt switch), but it does not say how the bound changes when the flag is false, nor what the returned quantity looks 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?

The content is compact and front-loaded with the German statement of purpose before the English restatement. The bilingual duplication of essentially the same sentence costs some space, but nothing is padded and no sentence is 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 six-required-parameter computation with no output schema, the description leaves the return value entirely unexplained — an agent cannot tell whether it receives a single bound, a pair of bounds, or a boolean outcome, and the 'verified vs unverified' branch semantics are not spelled out. Inputs themselves are fully covered by the 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 description coverage is 100%, so every one of the six required parameters (a_w, b_w, rest_a_w, rest_b_w, offset_grenze_w, gleicher_offset_belegt) is already documented in the schema. The description adds only the conceptual framing of 'common offset vs run-dependent error' and does not clarify units, combination rules, or how the two rest_* values interact with offset_grenze_w beyond what the schema states.

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 action on a specific resource: separating the verified common additive measurement error from run-dependent errors when bounding a power difference in an A/B comparison. It is clear enough to distinguish this computational tool from the sibling measurement tools, though it never names an alternative or states what the bound actually is.

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 only implied: the phrase 'with or without verified common-mode cancellation' implies the tool is for A/B comparisons where it is uncertain whether both readings share the same offset. There is no explicit 'use this when' condition, no statement of when the simpler/other measurement evaluation tool would be preferred, and no prerequisites for gathering the inputs.

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