Skip to main content
Glama

getecoback-raumklima

trockner_freigabe_nach_schichtwechsel_kontakt

Read-only

Vor einer frühen Trocknerübergabe prüfen, ob jemand die Freimeldung in einem bestätigten Kontaktfenster absetzen kann — Check a verified notification handoff before the next dryer reservation.

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": {
      "betriebsende_min": "<betriebsende_min>",
      "besitzer_erreichbar_bis_min": "<besitzer_erreichbar_bis_min>",
      "folgeperson_erreichbar_ab_min": "<folgeperson_erreichbar_ab_min>",
      "folgetermin_min": "<folgetermin_min>",
      "bestaetigte_uebergabe": "<bestaetigte_uebergabe>"
    },
    "name": "trockner_freigabe_nach_schichtwechsel_kontakt"
  }
}

Input Schema

NameRequiredDescriptionDefault
folgetermin_minYesBeginn der anschließenden Buchung auf derselben Zeitachse.
betriebsende_minYesFrüheste beobachtete Freimeldung nach vollständigem Programm und notwendiger Entnahme.
bestaetigte_uebergabeYesBeide haben die Freimeldung als Übergabe vereinbart.
besitzer_erreichbar_bis_minYesBis zu dieser Minute kann die bisherige Person nachsehen und persönlich Bescheid geben.
folgeperson_erreichbar_ab_minYesAb dieser Minute kann die Folgeperson die Freimeldung erhalten.

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?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, closed-world check. The description reinforces that by saying it verifies whether a notification can be placed, but it does not explain what the result means, what happens when the check fails, or how the contact-window feasibility is determined.

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 and front-loads the trigger condition, but it presents the same sentence in German and then English. That bilingual duplication is understandable for accessibility, yet it does not add new information and slightly weakens conciseness.

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-parameter, fully required feasibility check, the description explains the scenario but omits what the tool returns. Since there is no output schema, the agent must infer that the result is a yes/no feasibility outcome from the word 'prüfen' alone.

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%, so the individual parameters are already well documented. The description adds scenario-level meaning by tying them to a confirmed contact window and an upcoming dryer reservation, but it does not add parameter-specific detail 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 states a specific check: whether someone can issue a release notification within a confirmed contact window before the next dryer reservation. It clearly frames the tool as a verification rather than an action, though it does not explicitly distinguish itself from the many sibling Freigabe tools.

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?

It gives a clear trigger — before an early dryer handover and before the next dryer reservation — but offers no explicit exclusions or named alternatives among the sibling tools. Usage is implied by timing context rather than a full when-to-use/when-not-to-use rule.

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