Skip to main content
Glama

getecoback-raumklima

kompaktspuel_trockenziel_kunststoff_und_sonstige_teilsets

Read-only

Prüft nach einer dokumentierten Extra-Trocknen-Nutzung, welche benötigte Teilgruppe noch eigene Trocknungsarbeit hatte — Record which required dish group still needed drying work after a documented Extra Dry run.

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": {
      "option_belegt": "<option_belegt>",
      "kunststoff": "<kunststoff>",
      "andere_teile": "<andere_teile>"
    },
    "name": "kompaktspuel_trockenziel_kunststoff_und_sonstige_teilsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kunststoffYesBeleg für zur Nutzung benötigte geeignete Kunststoffteile.
andere_teileYesBeleg für andere benötigte Stücke zum gleichen selbst gesetzten Nutzungszeitpunkt.
option_belegtYesOption und der tatsächlich erprobte Programmzustand waren für das vorhandene Gerät dokumentiert?

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 the meaningful precondition that a documented Extra Dry run must exist, but the English gloss 'Record' slightly implies a write and is never reconciled with the read-only annotation, and no return shape is described.

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?

Very short and front-loaded, with the precondition stated before the outcome. The German/English duplication costs a little space, but the two versions are a single compact thought rather than padding.

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?

With three required parameters fully documented in the schema and read-only behavior covered by annotations, the essentials are present. However, there is no output schema and the description does not say what result is returned (which group, in what form), leaving a gap for the agent after the call.

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 both enum parameters document what each state means, so the schema carries the burden. The description adds nothing about option_belegt, kunststoff or andere_teile beyond what the schema already states, which is the expected baseline here.

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 German sentence names a specific verb+resource: it checks/records which required partial dish group still needed its own drying work after a documented Extra Dry run. That is concrete enough to tell what the tool produces, though it never contrasts itself with the many sibling kompaktspuel_* tools that cover adjacent sub-questions.

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 precondition 'nach einer dokumentierten Extra-Trocknen-Nutzung' implicitly tells the agent when this tool applies (only after a documented Extra Dry run). There is no explicit when-not guidance and no named alternative among the siblings, so the routing decision is left to inference.

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