Skip to main content
Glama

getecoback-raumklima

kuechenprogramm_gleiches_ende_schwankung_messen

Read-only

Für dieselbe Ausgabe zwei gewählte Programme nach eigener Messstreuung und kleinster belegter Differenz vergleichen — Compare observed energy ranges from repeated runs with the same outcome.

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_min_wh": "<a_min_wh>",
      "a_max_wh": "<a_max_wh>",
      "b_min_wh": "<b_min_wh>",
      "b_max_wh": "<b_max_wh>",
      "ergebnis_und_messaufbau_gleich": "<ergebnis_und_messaufbau_gleich>"
    },
    "name": "kuechenprogramm_gleiches_ende_schwankung_messen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_max_whYesGrößter beobachteter Bedarf dieser Läufe.
a_min_whYesKleinster beobachteter Bedarf bei mehreren vollständigen Läufen A.
b_max_whYesGrößter beobachteter Bedarf dieser Läufe.
b_min_whYesKleinster beobachteter Bedarf bei mehreren vollständigen Läufen B.
ergebnis_und_messaufbau_gleichYesDie tatsächliche Menge, das Nutzungsziel und Messgrenzen waren vergleichbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety and locality are covered. The description adds that comparison is based on measurement spread and the 'kleinste belegte Differenz' (smallest evidenced difference), which hints at how the verdict is formed, but it never states what the tool actually returns or how the two ranges are adjudicated. Some behavioral value, but the core output semantics remain undisclosed.

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?

The definition is short, but the German and English halves are near-duplicates rather than complementary, and the German clause 'nach eigener Messstreuung und kleinster belegter Differenz' is dense jargon that the English does not really clarify. Front-loading the verb 'vergleichen/compare' is good, but the redundancy costs a point.

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?

With five required parameters and no output schema, the description should at minimum say what the comparison yields (a verdict, a difference interval, a recommendation). It instead only describes inputs and the comparison premise, leaving the agent unable to predict the result shape. Adequate for invoking the tool, incomplete for interpreting it.

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 five parameters documented (including which runs are A versus B and the comparability flag), so the schema does the heavy lifting. The description frames the parameters as two program ranges plus an outcome-equality condition but adds no format, unit, or edge-case meaning beyond that. Baseline 3 is appropriate.

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 (compare) on a concrete object (observed energy ranges of two programs from repeated runs with the same outcome), so the agent knows it is a two-program spread comparison rather than a single measurement. It does not name any sibling tool or state what distinguishes it from the many other measurement-comparison siblings, so it stops short of a 5.

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 explicit when-to-use or when-not-to-use guidance and no alternative tool is mentioned. The only usage signal is the precondition 'same outcome / comparable measurement setup', which is already encoded as the required boolean parameter ergebnis_und_messaufbau_gleich, so the description contributes nothing beyond the schema on this dimension.

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