Skip to main content
Glama

getecoback-climate-weather

geraetemessung_vorzyklus_nachwirkung

Read-only

Beim gleichen Gerätemodus prüfen, ob der vorherige Modus den Startzustand sichtbar verändert — Compare the same target mode after two different predecessor modes.

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_nach_a_kwh": "<a_nach_a_kwh>",
      "a_nach_b_kwh": "<a_nach_b_kwh>",
      "pruefgrenze_kwh": "<pruefgrenze_kwh>",
      "gleiche_wartezeit": "<gleiche_wartezeit>"
    },
    "name": "geraetemessung_vorzyklus_nachwirkung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_nach_a_kwhYesEnergie eines A-Laufs nach einem vorherigen A-Lauf, in kWh.
a_nach_b_kwhYesEnergie eines A-Laufs nach einem vorherigen B-Lauf, in kWh.
pruefgrenze_kwhYesEigene absolute Prüfgrenze, in kWh, unter Berücksichtigung der Messstreuung.
gleiche_wartezeitYesWar der Abstand zum vorherigen Lauf in beiden Fällen gleich?

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 agent knows this is a safe, closed-world computation, and the description does not contradict that. It adds useful framing (the comparison is between a run after A and a run after B, judged against a user-supplied tolerance), but says nothing about what the result looks like or how a borderline case is treated.

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?

A single front-loaded sentence with the operative check stated first. The bilingual duplication (German then an English gloss) is redundant for a reader who understands either, but it does aid disambiguation and costs little space.

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?

All four required parameters are documented and the safety profile is covered by annotations, but with no output schema the description should say what the tool returns (a boolean verdict? a verdict plus measured difference?) and it does not. For a self-contained comparison/computation tool this leaves a real gap.

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 each parameter already carries a clear German description, so the schema does the heavy lifting. The description adds the conceptual pairing of the two kWh inputs (same target mode, different predecessor) but no syntax, units, or threshold-selection guidance 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 names a concrete operation: check whether the predecessor mode visibly changes the starting state of the same target mode, i.e. compare the same mode after two different predecessor modes. That is a specific verb+resource, not a restatement of the opaque name. It does not, however, distinguish this from any of the many neighbouring measurement/plausibility tools.

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?

There is no statement of when to use this check versus alternatives, no prerequisites (e.g. that two runs were already recorded), and no exclusions. The agent must infer the scenario entirely from the phrase 'nach zwei unterschiedlichen Vorgängermodi'.

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