Skip to main content
Glama

getecoback-climate-weather

stromzaehler_wechsel_protokoll

Read-only

Verbrauch über einen Stromzählerwechsel aus den getrennten Ständen berechnen. — Reconcile energy across a documented meter replacement.

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": {
      "alt_start": "<alt_start>",
      "alt_ausbau": "<alt_ausbau>",
      "neu_einbau": "<neu_einbau>",
      "neu_ende": "<neu_ende>"
    },
    "name": "stromzaehler_wechsel_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_endeYesAktueller Endstand des Neuzählers in kWh.
alt_startYesStand des Altzählers zu Beginn in kWh.
alt_ausbauYesSchlussstand des Altzählers laut Übergabeprotokoll in kWh.
neu_einbauYesAnfangsstand des Neuzählers laut Übergabeprotokoll in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed calculation. The description adds that the calculation reconciles energy from documented replacement readings, which is useful context, but it does not describe output format, rounding, or edge-case behavior.

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 definition is two short, front-loaded sentences with no waste. The bilingual German/English duplication is mildly redundant but does not obscure the calculation purpose.

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 simple read-only calculation with four fully documented required parameters, the description states the operation and the expected result, energy consumption. It could be more complete by explicitly stating the arithmetic combination of old and new readings, but no major gap remains.

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?

The input schema has 100% description coverage, including all four required kWh readings. The description's reference to 'getrennten Ständen' loosely maps to the old-start, old-final, new-initial, and new-final parameters, but adds no syntax or constraints 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?

The description uses a specific verb and resource: calculating energy consumption across a meter replacement from separate readings. It is clearly distinct in scope from sibling tools about pulse power or double-register reconciliation, though it does not explicitly name 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 phrase 'über einen Stromzählerwechsel aus den getrennten Ständen', meaning the tool applies when old and new meter readings are documented at replacement. There is no explicit when-to-use or when-not guidance and no named alternative.

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