Skip to main content
Glama

getecoback-raumklima

verbrauchstest_zielmenge_unterdeckung

Read-only

Prüfe, ob ein niedriger Energieverbrauch nur durch weniger erledigte Nutzmenge entstanden sein kann — Check whether a lower energy figure reflects lower delivered quantity

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_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "a_nutzmenge": "<a_nutzmenge>",
      "b_nutzmenge": "<b_nutzmenge>",
      "vergleichbares_ergebnis": "<vergleichbares_ergebnis>"
    },
    "name": "verbrauchstest_zielmenge_unterdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesFür A gemessene Energie in kWh
b_kwhYesFür B gemessene Energie in kWh
a_nutzmengeYesBei A vollständig erledigte Nutzmenge in einer gemeinsamen Einheit
b_nutzmengeYesBei B vollständig erledigte Nutzmenge in derselben Einheit
vergleichbares_ergebnisYesQualität und Definition der erledigten Nutzmenge sind 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; the description adds the interpretive framing (energy reduction vs. reduced delivered work). It does not, however, say what the check returns or what criterion decides that a shortfall 'can' explain the difference, which matters for a tool with no output schema.

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 condition stated before the gloss; no filler. The German/English duplication costs length but serves bilingual robustness, so it is defensible rather than wasteful.

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?

Five required numeric/boolean parameters and no output schema mean the description should clarify the shape of the verdict (boolean, ratio, explanatory share) and the comparability precondition. It conveys the intent well but leaves the agent guessing what comes back, so it is adequate but not complete for this tool's complexity.

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 all five parameters (a_kwh, b_kwh, a_nutzmenge, b_nutzmenge, vergleichbares_ergebnis) already carry units and constraints. The description echoes the two core concepts in both languages but adds no new unit, comparability, or edge-case semantics beyond the schema, fitting the baseline 3.

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 bilingual description states a concrete verb ('Prüfe'/check) plus the exact proposition being tested: whether a lower energy figure is explained by a lower delivered useful quantity. That is a recognizable, self-contained diagnostic purpose distinguishable from the surrounding measurement/estimation siblings, though it never names which sibling it contrasts 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-to-use guidance and no alternative named. Usage is only inferable from the wording ('ob ein niedriger Energieverbrauch ... entstanden sein kann'), which implies a two-scenario A/B comparison, but the agent must guess the trigger conditions and any preconditions beyond the schema's 'vergleichbares_ergebnis' flag.

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