Skip to main content
Glama

getecoback-climate-weather

laptop_strommessung_akku_startsaldo_proben

Read-only

Zwei Steckdosenmessungen bei gleicher Laptop-Aufgabe nach protokollierter Ladestandsänderung auf trennbare Bilanz prüfen — Flag unequal battery movement as a confound in two plugged-in laptop energy records.

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_start_pct": "<a_start_pct>",
      "a_ende_pct": "<a_ende_pct>",
      "b_start_pct": "<b_start_pct>",
      "b_ende_pct": "<b_ende_pct>",
      "toleranz_pp": "<toleranz_pp>",
      "akkuanzeige_vergleichbar": "<akkuanzeige_vergleichbar>"
    },
    "name": "laptop_strommessung_akku_startsaldo_proben"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ende_pctYesEntsprechende Anzeige am Ende von A.
b_ende_pctYesEntsprechende Anzeige am Ende von B.
a_start_pctYesAnzeige des Akkus vor Lauf A in Prozent.
b_start_pctYesAnzeige vor Lauf B in Prozent.
toleranz_ppYesEigene kleinste unterscheidbare Veränderung der Anzeige in Prozentpunkten.
akkuanzeige_vergleichbarYesDasselbe Gerät, dieselbe Akkuanzeige und vergleichbare Ablesebedingungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 and the bar is lower. The description adds real behavioral context beyond that — it discloses that unequal battery movement is treated as a confound to be flagged, which tells the agent what the verdict is about. It does not say what the returned judgement looks like or how toleranz_pp and akkuanzeige_vergleichbar gate the result, and with no output schema that is a 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with an English gloss, and the key action is front-loaded. However, the German half is dense terminology ('trennbare Bilanz', 'protokollierter Ladestandsänderung') and the English half largely restates it rather than adding new information, so wording is not fully economical.

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 six-parameter, all-required analysis tool with no output schema, the description covers the input situation and the intended finding (unequal battery movement as confound). It is silent on the result shape and on how the tolerance and comparability inputs affect the outcome, which an agent would want before invoking it in a measurement workflow.

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%, with each of the six parameters individually documented in the schema, so baseline is 3. The description adds only the framing that the charge-level change is 'protokolliert' and that the balance must be 'trennbar', hinting at the role of toleranz_pp and the comparability boolean, but it gives no extra syntax, units, or edge-case meaning for those values.

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 both the resource (two Steckdosenmessungen / plugged-in laptop energy records under the same laptop task) and the operation (check for a separable balance, flag unequal battery movement). The English gloss clarifies the otherwise jargon-heavy 'trennbare Bilanz', so an agent can tell this is a cross-run comparison/confound check rather than a raw measurement tool. It does not name or differentiate against any sibling explicitly.

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 stated preconditions: two runs, same laptop task, documented charge-level change, both plugged in. There is no explicit statement of when not to use it, nor a pointer to an alternative sibling for the case where battery movement cannot be separated or where only a single run exists.

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