Skip to main content
Glama

getecoback-raumklima

trocknung_rueckstand_fertigmeldungen

Read-only

Eine Wochenmessung mit begonnenen und fertig getrockneten Ladungen gegen den offenen Rückstand abgleichen — Reconcile the drying-work queue before comparing energy per finished batch.

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": {
      "offen_start": "<offen_start>",
      "begonnen": "<begonnen>",
      "fertig": "<fertig>",
      "abgebrochen": "<abgebrochen>",
      "endbestand_gesehen": "<endbestand_gesehen>"
    },
    "name": "trocknung_rueckstand_fertigmeldungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fertigYesIn diesem Zeitraum tatsächlich fertig getrocknete Ladungen.
begonnenYesNeu in Bearbeitung genommene Ladungen im betrachteten Zeitraum.
abgebrochenYesIn diesem Zeitraum abgebrochene, ausdrücklich als erledigt entfernte Ladungen.
offen_startYesLadungen, die bei Beginn schon in Bearbeitung waren.
endbestand_gesehenYesAm Ende tatsächlich gezählte noch in Bearbeitung befindliche Ladungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety profile is covered. The description adds that this is a consistency check performed before further analysis, but it never says what happens on a mismatch or what the result looks like — the key behavioral question for a reconciliation tool.

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?

Two short sentences with no filler, and the action is front-loaded. The German and English halves are not strict translations — the English contributes the downstream-timing condition — so the bilingual form adds a little rather than merely repeating, though it is slightly awkward.

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 five-required-parameter, no-output-schema tool, the definition omits what the reconciliation actually returns or how discrepancies are surfaced, which an agent needs in order to interpret the call. It is adequate for selecting the tool but thin for predicting its result.

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 one of the five required counters is documented in German, so the schema carries the parameter burden. The description gestures at 'begonnen', 'fertig' and 'offener Rückstand' but says nothing about 'abgebrochen' or 'endbestand_gesehen', adding essentially no meaning beyond the schema.

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 names a concrete operation and resource: reconciling a weekly count of 'begonnen' and 'fertig getrocknet' loads against the open backlog ('gegen den offenen Rückstand abgleichen'). It is clear enough to know this is a balance/roll-forward reconciliation, but it offers no explicit differentiation from the many sibling drying tools, and the jargon ('Rückstand', 'Fertigmeldungen') makes the exact output ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'before comparing energy per finished batch' gives a sequencing condition, implying this should be run prior to downstream energy-per-batch analysis. There is no statement of when not to use it, no prerequisites, and no named alternative among the siblings that touch drying counts.

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