Skip to main content
Glama

getecoback-raumklima

kleiderschrank_einraeumen_trockenkontrolle

Read-only

Trockene und ausstehende Textilien auf Lagerplatz und getrennte Nachkontrolle verteilen — Allocate only confirmed-dry pieces to a ventilated wardrobe plan.

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": {
      "freie_stellplaetze": "<freie_stellplaetze>",
      "trocken": "<trocken>",
      "naht_pruefen": "<naht_pruefen>",
      "trocknet": "<trocknet>",
      "beobachtung": "<beobachtung>"
    },
    "name": "kleiderschrank_einraeumen_trockenkontrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
trockenYesSaubere trockene Stücke mit abgeschlossener Kontrolle.
trocknetYesWeitere Stücke, die noch trocknen.
beobachtungYesZustand des Lagerorts.
naht_pruefenYesWeitere Stücke mit noch nicht kontrollierten Nähten oder dicken Stellen.
freie_stellplaetzeYesTatsächlich freie Plätze mit unverstellten Luftwegen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, but the description muddies it: 'einraeumen' and 'verteilen' read like a physical placement mutation, while the gloss says 'plan.' The description does not resolve whether an allocation is computed or a wardrobe is actually filled, and says nothing about capacity limits or what happens to the still-drying and seam-unchecked counts.

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?

It is short, but the German original and the English gloss are near-duplicates rather than complementary, and the German clause ('auf Lagerplatz und getrennte Nachkontrolle verteilen') front-loads an ambiguous target before the clarifying English sentence. Trimming to a single precise sentence would improve it.

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 five required parameters, no output schema, and a read-only allocation computation, the description never says what the tool returns (a placement plan? counts?) or how free Stellplätze constrain the result. For a tool whose entire value is the produced allocation, that omission is significant.

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 all five parameters are documented in the schema; the description's dry versus pending distinction loosely maps to trocken/trocknet and naht_pruefen but adds no syntax, units, or interaction rules. Baseline 3 applies when the schema already carries parameter meaning.

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 English gloss states a specific verb and resource: 'Allocate only confirmed-dry pieces to a ventilated wardrobe plan,' with an explicit eligibility qualifier. The German half adds 'Lagerplatz' and 'getrennte Nachkontrolle' as targets, which is more diffuse but still on-purpose. It does not distinguish the tool from wardrobe-related siblings such as kleiderschrank_luftweg_hinter_stapel or kleiderschrank_stapel_zugriffsreserve.

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?

The description gives an eligibility rule ('only confirmed-dry pieces') but no when-to-use/when-not guidance and no indication of how it relates to the sibling wardrobe tools or to any prerequisite dry-check step. An agent must infer ordering and alternatives from the name and parameters alone.

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