Skip to main content
Glama

getecoback-raumklima

stromversuch_streuung_gruppen_zusammen

Read-only

Standardabweichung zweier gleich abgegrenzter Versuchsgruppen aus Anzahlen, Mittelwerten und Gruppenstreuungen kombinieren — Pool individual energy-run variation while preserving between-group differences.

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_laeufe": "<a_laeufe>",
      "b_laeufe": "<b_laeufe>",
      "a_mittel_kwh": "<a_mittel_kwh>",
      "b_mittel_kwh": "<b_mittel_kwh>",
      "a_stichprobe_sd_kwh": "<a_stichprobe_sd_kwh>",
      "b_stichprobe_sd_kwh": "<b_stichprobe_sd_kwh>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "stromversuch_streuung_gruppen_zusammen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_laeufeYesZahl gültiger unabhängiger Messläufe in A.
b_laeufeYesZahl gültiger unabhängiger Messläufe in B.
a_mittel_kwhYesVerbrauchsmittel A in kWh.
b_mittel_kwhYesVerbrauchsmittel B in kWh.
vergleichbarYesSind Messendpunkt, Aufgabe und Einheit gleich sowie die Versuche überschneidungsfrei?
a_stichprobe_sd_kwhYesStichproben-Standardabweichung A in kWh, berechnet mit n−1.
b_stichprobe_sd_kwhYesStichproben-Standardabweichung B in kWh, berechnet mit n−1.

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 agent knows this is a safe, closed computation, which lowers the bar. The description adds no behavior beyond that: it does not say what is returned (pooled SD in kWh, degrees of freedom), nor what happens when 'vergleichbar' is false, which is the single most consequential behavioral detail for a 7-required-param tool.

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?

Two sentences, but the second is a language-mixed restatement whose 'preserving between-group differences' clause is ambiguous for a pooled-SD tool and can mislead about whether means are combined. The front-loaded German clause is fine; the trailing English gloss does not earn its place.

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 7-required-parameter computation with no output schema, the description should state the result (a single pooled standard deviation, in kWh) and the failure mode for 'vergleichbar'=false. It covers the inputs but stops short of what an agent needs to invoke this correctly and interpret the outcome.

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 every parameter is already documented with units and ranges, making 3 the baseline. The description's mapping of 'Anzahlen, Mittelwerten, Gruppenstreuungen' onto the parameter families adds only marginal meaning 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 German clause names a specific verb (kombinieren) and resource (Standardabweichung zweier Versuchsgruppen) and enumerates the inputs used (Anzahlen, Mittelwerte, Gruppenstreuungen), so an agent knows this computes a pooled dispersion measure. It does not differentiate itself from any sibling, and the English follow-up ('pool individual energy-run variation while preserving between-group differences') muddies rather than sharpens the purpose.

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 phrase 'zweier gleich abgegrenzter Versuchsgruppen' plus the required 'vergleichbar' flag imply the usage precondition (two comparable, non-overlapping runs), but the description never states when to pick this over alternatives or what to do when the groups are not comparable. Guidance is inferable but not explicit.

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