Skip to main content
Glama

getecoback-raumklima

stromzaehler_intervalltempo_ungleiche_abstaende

Read-only

Verbrauchstempo zwischen ungleich weit auseinanderliegenden kumulierten Stromablesungen vergleichen — Compare observed slope rather than raw differences in a three-point meter history.

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": {
      "erster_stand_kwh": "<erster_stand_kwh>",
      "mittlerer_stand_kwh": "<mittlerer_stand_kwh>",
      "letzter_stand_kwh": "<letzter_stand_kwh>",
      "erstes_intervall_h": "<erstes_intervall_h>",
      "zweites_intervall_h": "<zweites_intervall_h>"
    },
    "name": "stromzaehler_intervalltempo_ungleiche_abstaende"
  }
}

Input Schema

NameRequiredDescriptionDefault
erster_stand_kwhYesErster bestätigter Stand eines unveränderten Registers.
letzter_stand_kwhYesDritter bestätigter Stand desselben Registers.
erstes_intervall_hYesEchte Stunden zwischen den ersten beiden Ablesungen.
mittlerer_stand_kwhYesNachfolgender bestätigter Stand desselben Registers.
zweites_intervall_hYesEchte Stunden zwischen den letzten beiden Ablesungen.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a slope comparison over a three-point history, but it does not explain output format, handling of non-monotonic readings, or other edge cases.

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 description is compact and front-loads the core comparison concept. The bilingual phrasing repeats the same idea but does not obscure the main point.

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 five-parameter read-only calculation with no output schema, the description sufficiently conveys that the tool compares observed slope across unequally spaced readings. It could say more about the expected numeric result or validation behavior, but the essential purpose is clear.

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 the input schema already documents all five parameters in detail. The description reinforces the three-point structure and unequal interval concept but adds no parameter-specific 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 states a specific operation: comparing consumption rate (slope) between unequally spaced cumulative electricity readings in a three-point history. It clearly distinguishes the method from using raw differences, though it does not explicitly differentiate itself from sibling meter tools.

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?

The description implies the tool should be used when meter readings are unequally spaced and when slope comparison is preferable to raw differences. It does not provide explicit when-not-to-use guidance or name a specific alternative tool.

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