Skip to main content
Glama

getecoback-climate-weather

haushaltsgeraet_ersatz_unabhaengige_engpaesse

Read-only

Ersatz vorerst verschieben, wenn die tatsächlich knappen Arbeitsgänge durch bestätigte Terminwechsel abgedeckt werden — Check whether rescheduling covers only transferable 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": {
      "leistung_bestaetigt": "<leistung_bestaetigt>",
      "heute_fest": "<heute_fest>",
      "heute_verschiebbar": "<heute_verschiebbar>",
      "heute_platz": "<heute_platz>",
      "morgen_fest": "<morgen_fest>",
      "morgen_platz": "<morgen_platz>"
    },
    "name": "haushaltsgeraet_ersatz_unabhaengige_engpaesse"
  }
}

Input Schema

NameRequiredDescriptionDefault
heute_festYesHeute zwingend fällige gleichartige Aufgaben.
heute_platzYesBestätigte Gerätekontingente für heute.
morgen_festYesMorgen bereits zwingend fällige Aufgaben.
morgen_platzYesBestätigte Gerätekontingente morgen.
heute_verschiebbarYesZusätzliche Aufgaben, die erst morgen enden dürfen.
leistung_bestaetigtYesSind Gerät, Aufgaben und alle angegebenen Einsatzkapazitäten tatsächlich bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 safety is covered and the description does not need to repeat it. The text adds the evaluation context ("only transferable workload") but never says what the tool returns, which matters because there is no output schema and the word "Check" implies a verdict.

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 it is a single dense hybrid German/English sentence whose two halves restate the same idea in different words rather than front-loading a clear statement of purpose. Nothing is padded, yet the phrasing is harder to parse than the length warrants.

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?

With six required parameters, no output schema, and a boolean-style check, the description should say what the answer means (e.g. under which parameter constellation the postponement is safe). It leaves the agent to infer the evaluation logic entirely from the schema field names.

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 every parameter carries a German description, so the schema already does the explanatory work. The description adds no mapping between its concepts ("bestätigte Terminwechsel", "übertragbare Arbeit") and the six fields, so it does not exceed the baseline.

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 ("Ersatz vorerst verschieben" / "Check whether rescheduling covers only transferable workload") but the object of the check stays abstract — it is unclear whether the tool postpones anything or only evaluates a boolean condition. It is not a tautology of the name, yet an agent cannot state precisely what the tool computes without reverse-engineering the parameter names.

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?

A decision condition is given ("wenn die tatsächlich knappen Arbeitsgänge durch bestätigte Terminwechsel abgedeckt werden"), which hints at the scenario, but there is no guidance on when to call this versus the many sibling Engpass/Ersatz tools and no stated preconditions or exclusions.

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