Skip to main content
Glama

getecoback-climate-weather

pflege_spuelstelle_separater_ruecklauf

Read-only

Erneute Arbeit an einer bereits quittierten Spülstelle ohne Rückführung fertiger Teile planen — Isolate only the pieces affected when a rinse step must be revisited.

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": {
      "betroffene_zugeordnet": "<betroffene_zugeordnet>",
      "bereits_getrennt_fertig": "<bereits_getrennt_fertig>",
      "gruppenreste": "<gruppenreste>",
      "zustand_unklar": "<zustand_unklar>"
    },
    "name": "pflege_spuelstelle_separater_ruecklauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
gruppenresteYesWeitere Teile, deren dokumentierter Spülschritt unvollständig ist.
zustand_unklarYesWeitere Teile ohne nachvollziehbaren Bearbeitungsstand.
betroffene_zugeordnetYesSind die von der Unterbrechung betroffenen Teile eindeutig zugeordnet?
bereits_getrennt_fertigYesVor der Unterbrechung fertig geprüfte und separat weggelegte Teile.

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 real scope context — finished parts are not returned ('ohne Rückführung fertiger Teile') and only affected pieces are isolated — but says nothing about what the tool actually produces from the four counts, which matters for a planning tool with no output schema.

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 compact clauses with the scenario stated first and the isolation constraint second; nothing is padding. The German/English split is slightly redundant in phrasing but each half contributes a distinct fact, so it remains efficient.

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, read-only, closed-world tool, the definition covers the trigger and the scope constraint. It does not state what the planned result or response looks like and no output schema exists to fill that gap, leaving an agent unsure what it receives after supplying the four required values.

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%, with each of the four parameters (betroffene_zugeordnet, bereits_getrennt_fertig, gruppenreste, zustand_unklar) individually documented. The description adds no further meaning to any of them, so the baseline 3 applies when the schema carries the full explanatory burden.

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 specific action and object: planning renewed work at an already acknowledged rinse station ('Erneute Arbeit an einer bereits quittierten Spülstelle ... planen'), narrowed by 'ohne Rückführung fertiger Teile'. It is clearly a planning/isolation tool rather than an execution tool, though the heavy domain jargon and the lack of any explicit contrast to the many pflege_* siblings keep it just short of 5.

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 'when a rinse step must be revisited' gives a recognizable trigger condition for use. However, there is no guidance on when NOT to use it and no pointer to any of the numerous sibling pflege_* tools that might otherwise be the right choice, so the agent must infer routing on its own.

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