Skip to main content
Glama

getecoback-climate-weather

stromzaehler_impulsleistung

Read-only

Mittlere Bezugsleistung aus gezählten sichtbaren Zählerimpulsen ableiten. — Estimate average import power from an optical meter pulse count without touching the installation.

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": {
      "impulse": "<impulse>",
      "impulse_pro_kwh": "<impulse_pro_kwh>",
      "sekunden": "<sekunden>"
    },
    "name": "stromzaehler_impulsleistung"
  }
}

Input Schema

NameRequiredDescriptionDefault
impulseYesGezählte Impulse des Bezugszählers.
sekundenYesBeobachtungsfenster in Sekunden.
impulse_pro_kwhYesAm Zähler angegebene Impulse pro kWh.

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 readOnlyHint=true and openWorldHint=false, so safety is largely covered; the description reinforces it with the non-invasive 'without touching the installation' framing. It adds that the result is an average over an observation window, which is useful behavioral context. It does not disclose that this is a pure offline calculation, nor the unit of the returned power value, which is the main remaining gap.

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 with the core purpose front-loaded, followed by the non-invasiveness qualifier. The German statement and the English translation are semantically redundant, but the duplication is brief and arguably aids a bilingual agent rather than bloating the definition.

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 three-required-parameter pure calculation with no output schema and full schema coverage, the description covers the what and the safety posture. It is incomplete on the one thing an agent cannot get from the schema: the output unit (W vs kW) and the fact that the result is a derived average rather than a measured instantaneous value. Those are meaningful omissions for a calculation tool, even if minor.

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%, and all three parameters carry German descriptions plus min/max bounds, so the schema does the heavy lifting. The description adds no syntax, unit, or interpretation detail beyond what the schema already provides (e.g., that impulses must be from a visible import register and sekunden defines the averaging window). Baseline 3 is appropriate.

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 computation and its inputs: derive average import power (Bezugsleistung) from counted optical meter pulses. That is far more precise than the tool name alone and tells an agent what value comes out. It does not, however, distinguish itself from power-related siblings such as heizleistung_watt, so it stops short of a 5.

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 rather than stated: an agent can infer this applies when a meter with a visible pulse LED and a stated impulse-per-kWh constant is available and the installation must not be touched. There is no explicit when-not guidance, no mention of alternatives for cases where pulses cannot be counted, and no prerequisites beyond the phrasing 'ohne die Installation zu berühren'.

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