Skip to main content
Glama

getecoback-climate-weather

kompaktspuel_stromvergleich_teilaufgabe_untergrenze

Read-only

Prüft ob der gemessene Kompakt-Teil schon den Verbrauch der vollständigen bisherigen Aufgabe erreicht — Test whether the measured compact subset already uses the energy of the full existing workload.

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": {
      "bestand_kwh": "<bestand_kwh>",
      "kompakt_teil_kwh": "<kompakt_teil_kwh>",
      "messspiel_kwh": "<messspiel_kwh>",
      "teilaufgabe_abgeglichen": "<teilaufgabe_abgeglichen>"
    },
    "name": "kompaktspuel_stromvergleich_teilaufgabe_untergrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
bestand_kwhYesGemessene kWh einer vollständigen bisherigen Haushaltsaufgabe.
messspiel_kwhYesAbgeglichene Vergleichsbreite der beiden Zählerstände in kWh.
kompakt_teil_kwhYesBereits gemessene kWh der begonnenen Kompaktvariante ohne offenen Rest.
teilaufgabe_abgeglichenYesEs ist dieselbe gewünschte Arbeit, ein echter Teil der Aufgabe ist gemessen und der offene Rest kann nur Strom hinzufügen.

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 establish readOnlyHint=true and openWorldHint=false, so safety behavior is covered. The description adds the semantic condition being evaluated—compact subset versus full workload consumption—but does not describe the return value, thresholds, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence, with an English rendering after the em dash. It contains no filler and states the condition directly.

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 simple read-only predicate with fully documented parameters, the description explains the test adequately. However, with no output schema and no stated return semantics, the agent is left to infer what result the check produces and how to interpret 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?

All four parameters have detailed schema descriptions (100% coverage), so the schema already supplies their meanings, including bestand_kwh, kompakt_teil_kwh, messspiel_kwh, and teilaufgabe_abgeglichen. The description adds only the high-level relationship between two of them, not syntax or additional constraints.

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 states a specific comparison: whether the measured compact subset's kWh has already reached the full workload's consumption. The verb 'Prüft' and the two compared quantities make the resource and test clear, but no sibling alternative is named, so differentiation relies on the already specific tool name.

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?

It gives no explicit when-to-use or when-not-to-use guidance and does not route the agent among the many Kompaktspuel siblings. The implied usage is only that this is a lower-bound comparison check.

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