Skip to main content
Glama

getecoback-raumklima

strommessung_abba_abwechselnd

Read-only

A–B–B–A-Blöcke derselben Geräteaufgabe auswerten — Compare two appliance modes while balancing a linear order trend.

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_anfang_kwh": "<a_anfang_kwh>",
      "b_anfang_kwh": "<b_anfang_kwh>",
      "b_ende_kwh": "<b_ende_kwh>",
      "a_ende_kwh": "<a_ende_kwh>"
    },
    "name": "strommessung_abba_abwechselnd"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ende_kwhYesEnergie des letzten A-Laufs, in kWh.
b_ende_kwhYesEnergie des folgenden B-Laufs, in kWh.
a_anfang_kwhYesEnergie des ersten A-Laufs, in kWh.
b_anfang_kwhYesEnergie des anschließenden B-Laufs, in kWh.

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 one real behavioral fact — that a linear order trend is balanced out — which explains why the four values are supplied in ABBA order. It does not say what is returned (effect estimate, corrected difference) or whether the result is unit-bound to kWh.

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 tight clauses, front-loaded with the resource and design before the comparison goal. No filler, though the German and English clauses partially restate each other rather than each adding new information.

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 four-required-parameter read-only analysis tool with no output schema, the description explains the design but omits what the computed result represents and any validity conditions on the inputs. An agent could call it, but would not know what to expect back.

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 coverage is 100% and each parameter already carries a description, so the schema does the heavy lifting. The description only adds the sequencing rationale (first A, following B, last A, subsequent B) implicitly through the ABBA framing; no extra meaning such as whether these are cumulative meter readings or per-run consumption 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?

Names a specific operation ('auswerten') and a specific resource (A–B–B–A-Blöcke derselben Geräteaufgabe), and the second clause clarifies it is a comparison of two appliance modes with linear trend balancing. It is distinguishable from a generic A/B tool, though it does not explicitly name the sibling 'strommessung_a_b_messfehler' it differs from.

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?

The description gives no when-to-use condition, no prerequisite (e.g. runs must be complete and in order), and no exclusion pointing to an alternative tool. The agent must infer the scenario purely from the tool name and the ABBA design wording.

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