Skip to main content
Glama

getecoback-climate-weather

gruppenmessung_stichprobe_anteil_betriebsprofile

Read-only

Aus getrennt beobachteten Geräteanteilen für zwei Betriebsprofile einen belegten Gesamtanteil rekonstruieren — Weight device shares by aggregate energy in the matching profiles.

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_gruppe_wh": "<a_gruppe_wh>",
      "b_gruppe_wh": "<b_gruppe_wh>",
      "a_geraet_prozent": "<a_geraet_prozent>",
      "b_geraet_prozent": "<b_geraet_prozent>",
      "stichproben_passend": "<stichproben_passend>"
    },
    "name": "gruppenmessung_stichprobe_anteil_betriebsprofile"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_gruppe_whYesGemessene Gesamtenergie des gesamten Profils A.
b_gruppe_whYesGemessene Gesamtenergie des gesamten Profils B.
a_geraet_prozentYesRepräsentativ einzeln gemessener Geräteanteil innerhalb von Profil A.
b_geraet_prozentYesEntsprechend belegter Geräteanteil innerhalb von Profil B.
stichproben_passendYesSind beide Stichproben für ihr Profil belegt und überschneiden sich die Profile nicht?

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 and this is evidently a pure computation. The description adds that the result is 'belegt' (evidence-backed) and derived by energy weighting, but it does not disclose failure behavior for mismatched samples or the shape of the returned value.

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 compact clauses that lead with the purpose before the English gloss; nothing is padding. The bilingual duplication is slightly redundant but keeps the definition short and front-loaded.

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 no output schema, the description should clarify what is returned (a weighted percentage? a share of which profile?) and how stichproben_passend gates the computation; neither is stated. It is adequate for a simple read-only calculation tool but leaves the caller guessing about the result and the invalid-input path.

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 each parameter is already documented and the baseline is 3. The phrase 'Weight device shares by aggregate energy' does add real meaning — it explains that a_gruppe_wh/b_gruppe_wh act as weights against the percent values — but this is a marginal clarification rather than a full specification of the formula.

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?

States a specific operation (reconstruct a validated aggregate share from separately observed device shares across two operating profiles) with a clear verb and resource. It is distinguishable from the sibling measuring tools, though it never names a sibling it should not be confused with.

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 guidance and no alternative named. The precondition is only implied through the description's phrase 'getrennt beobachteten' and the stichproben_passend parameter; the description never says what the caller should do when that flag is false or when the profiles overlap.

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