Skip to main content
Glama

getecoback-raumklima

kompaktspuel_bestandsgeraet_kauf_bis_eigenbeleg

Read-only

Leitet einen prüfbaren Kauf- oder Behalten-Schritt aus der tatsächlich benötigten Haushaltsaufgabe ab — Decide whether to keep the existing setup or pursue verification for a compact replacement.

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": "<bestand>",
      "kompaktprobe": "<kompaktprobe>",
      "wechselgrund_belegt": "<wechselgrund_belegt>"
    },
    "name": "kompaktspuel_bestandsgeraet_kauf_bis_eigenbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
bestandYesBeobachtete Tauglichkeit des bestehenden Ablaufs für die volle Aufgabe.
kompaktprobeYesDerselbe Endpunkt in der geplanten oder bereits beobachteten Kompaktvariante.
wechselgrund_belegtYesEin getrennter konkreter Wechselgrund ist im eigenen Haushalt belegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'ableiten'/'decide' framing is consistent with a non-mutating derivation, so there is no contradiction. It adds the constraint that the step is 'prüfbar' and grounded in the actually needed household task, but says nothing about how the decision is expressed, whether it is deterministic, or what evidence is required for the 'offen' cases.

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 core statement is front-loaded and short, but the German sentence and its English rendering are near-duplicates rather than complementary, so half the text is redundant. Nothing extraneous beyond that, but the bilingual doubling wastes the limited space available.

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 only three fully documented enum/boolean parameters, annotations present and no nested objects, the definition is adequate to attempt a call. It stops short of describing the decision logic or the shape of the derived 'Schritt' (no output schema exists to cover that gap), which is the main thing an agent would still be guessing at.

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% and both enum parameters carry their own descriptions ('Beobachtete Tauglichkeit des bestehenden Ablaufs', 'Derselbe Endpunkt in der geplanten ... Kompaktvariante'), so the schema does the heavy lifting. The description adds no extra meaning about how bestand, kompaktprobe and wechselgrund_belegt combine into the keep-or-verify outcome, which is exactly the semantics an agent would need.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an action ('Leitet ... ab' / 'Decide') and an object ('Kauf- oder Behalten-Schritt' for a compact replacement derived from the actually required household task), so the general intent is graspable. However, it never distinguishes this derivation step from closely related siblings such as kompaktspuel_kaufentscheidung_pilot_mit_abbruchgrenze or kompaktspuel_bestandsgeraet-style comparisons, and the doubled German/English phrasing leaves the concrete artifact produced ambiguous.

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 statement of when this tool should be chosen, when it should not, or which alternative applies under which condition. The agent must infer from the name and the enum fields alone that this is the keep-vs-replace gate, with no exclusions or prerequisites given.

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