Skip to main content
Glama

getecoback-raumklima

strommessung_va_w_einordnen

Read-only

VA-Anzeige und W-Anzeige eines Steckdosenmessgeräts für dieselbe Messung auseinanderhalten. — Distinguish apparent power from the active power used for energy billing.

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": {
      "schein_va": "<schein_va>",
      "wirk_w": "<wirk_w>",
      "toleranz_w": "<toleranz_w>"
    },
    "name": "strommessung_va_w_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
wirk_wYesGleichzeitig gemessene Wirkleistung in W.
schein_vaYesGemessene Scheinleistung in VA.
toleranz_wYesAbsoluter Rundungs- und Messspielraum in W bzw. VA.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds domain context — that W is the quantity used for energy billing while VA is the apparent-power display — which goes beyond the annotations. It does not disclose what the call returns or how toleranz_w affects the outcome, which matters more here because no output schema exists.

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 short sentences, front-loaded with the core discrimination task. The German sentence and its English gloss are largely redundant, but the structure is clean and nothing is padded.

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?

For a three-parameter, fully documented read-only computation, the description supplies the domain framing (VA vs W, billing relevance) that the schema cannot. The main omission is any indication of the result shape, which is a real gap given there is no output schema, but the tool is simple enough that this is a minor rather than fatal shortfall.

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 three parameters (schein_va, wirk_w, toleranz_w) are already documented in the schema with units and bounds. The description adds no format, unit, or relationship detail beyond that, so the baseline of 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 specific discrimination task: separating the VA (apparent power) reading from the W (active power) reading of the same plug-meter measurement, and ties W to energy billing. That is concrete enough to distinguish it from numeric siblings like strommessung_a_b_messfehler or strommessung_hochrechnen. It stops short of saying what the tool actually produces (a verdict, a correction, a classification).

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 an implied context (a plug meter showing both VA and W for one measurement) but no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling. An agent must infer the triggering situation entirely from the phrasing 'auseinanderhalten'.

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