Skip to main content
Glama

getecoback-climate-weather

kontaktgrill_pflegegruppe_abtropfplatz

Read-only

Pflegefreigaben und Ablageplätze für Platten und Auffangbehälter als gemeinsamen Ablauf erfassen — Plan a cooling and cleaning handoff for only the documented removable components.

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": {
      "freigegebene_platten": "<freigegebene_platten>",
      "auffangbehaelter": "<auffangbehaelter>",
      "separate_plaetze": "<separate_plaetze>",
      "stapeln_ausgeschlossen": "<stapeln_ausgeschlossen>"
    },
    "name": "kontaktgrill_pflegegruppe_abtropfplatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
auffangbehaelterYesAnzahl laut Anleitung entnehmbarer Behälter mit geklärtem Pflegeweg.
separate_plaetzeYesVerfügbare passende Ablagen, wenn alle Teile einzeln abgelegt werden müssen.
freigegebene_plattenYesAnzahl laut Anleitung entnehmbarer Platten mit geklärtem Pflegeweg.
stapeln_ausgeschlossenYesEigene vorgesehene Pflege verlangt einzelne Ablageplätze und kein Stapeln.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The annotations (readOnlyHint=true, openWorldHint=false) already establish that this is a safe, closed-world lookup, and the description is broadly consistent with that. However 'erfassen' (record/capture) sits in mild tension with a read-only hint and could mislead an agent into expecting persistence. It adds the meaningful restriction that only manually documented removable parts count, but says nothing about what the computed result looks like.

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 opening clause is front-loaded with the relevant nouns, which is good. The English after the dash largely restates the German rather than adding information, and the mixed-language phrasing costs precision without shortening the text.

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 four-required-parameter computation with no output schema, the description should make clear what the agent receives (a feasibility verdict? a count of required slots?). It conveys the input side well via the schema but leaves the result and the interaction between separate_plaetze and stapeln_ausgeschlossen unexplained.

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 four parameters (freigegebene_platten, auffangbehaelter, separate_plaetze, stapeln_ausgeschlossen) are already documented with units, bounds and meaning. The description adds no further semantics such as how separate_plaetze relates to the plate/container counts, so the baseline holds.

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 pairs a plausible verb ('erfassen' / 'Plan a ... handoff') with a concrete resource (Pflegefreigaben und Ablageplätze für Platten und Auffangbehälter), so the domain is identifiable. But 'als gemeinsamen Ablauf' and 'cooling and cleaning handoff' are abstract, and nothing distinguishes it from near-identical siblings such as kontaktgrill_haeufigkeit_auffangbehaelter_protokoll or kontaktgrill_platten_spuelmaschine_beleg.

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?

There is no statement of when to pick this tool over the many kontaktgrill_* siblings, nor any prerequisite or exclusion beyond 'only the documented removable components'. That phrase is a useful scoping constraint but is not usage guidance in the routing sense.

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