Skip to main content
Glama

getecoback-climate-weather

vorhandenes_geraet_routine_und_sonderbedarf

Read-only

Ein vorhandenes Gerät behalten und ausschließlich die belegte Funktionslücke separat planen — Check whether a verified complement covers only the uncovered household tasks.

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": {
      "aufgaben_vergleichbar": "<aufgaben_vergleichbar>",
      "routine_je_woche": "<routine_je_woche>",
      "vorhanden_routine": "<vorhanden_routine>",
      "sonder_je_woche": "<sonder_je_woche>",
      "vorhanden_sonder": "<vorhanden_sonder>",
      "ergaenzung_sonder": "<ergaenzung_sonder>"
    },
    "name": "vorhandenes_geraet_routine_und_sonderbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
sonder_je_wocheYesGeplante Sondervorgänge pro Woche.
routine_je_wocheYesGeplante Routinevorgänge pro Woche.
vorhanden_sonderYesMit vorhandenem Gerät bestätigte Sondervorgänge pro Woche.
ergaenzung_sonderYesZusätzliche bestätigte Sondervorgänge durch vorhandene Ergänzung oder bereits verfügbare Leihoption.
vorhanden_routineYesMit vorhandenem Gerät bestätigte Routinen pro Woche.
aufgaben_vergleichbarYesSind die Aufgaben beider Geräte auf derselben Grundlage und im eigenen Haushalt geprüft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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. The description adds only a restatement of intent and does not disclose what the check actually decides, what constitutes a passing vs. failing coverage comparison, or that all six inputs are obligatory. With no output schema, the return values remain entirely opaque.

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 definition is short, but the German clause and the English clause after the dash restate essentially the same idea rather than complementing each other, so half the text is duplicated meaning. The core operation is not front-loaded clearly because the two halves frame it differently (a retention decision vs. a coverage check).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a six-parameter, all-required comparison/decision tool with no output schema, and the description never explains what result the agent receives or how to act on it. For a tool whose whole value is a verdict on coverage, that leaves a significant gap.

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% with all six parameters individually documented, so the schema carries the burden and baseline 3 applies. The description's mention of a 'belegte Funktionslücke' loosely maps to the vorhanden_/sonder_ pairs but adds no concrete interpretation beyond what the schema already states.

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 intent (retain an existing device) and an operation (plan only the documented functional gap separately / check whether a complement covers only uncovered tasks), but the phrasing is abstract domain jargon ('belegte Funktionslücke') and reads like a policy statement rather than a concrete operation. It offers no differentiation from closely related siblings such as geraet_wahl or geraet_bundle_aufpreis_gebrauchswert, so an agent cannot confidently place it in the family.

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 guidance on when this tool should be chosen over an alternative, no prerequisites, and no exclusions. The closest thing is an implied scenario ('keep an existing device'), but nothing tells the agent which sibling handles the adjacent cases.

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