Skip to main content
Glama

getecoback-raumklima

pflegeablage_sauber_schmutzig_nacheinander

Read-only

Einen gemeinsam genutzten Arbeitsplatz mit beobachtetem Freiräum- und Prüfschritt umstellen — Check a sequential switch between used and clean work materials.

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": {
      "belegt": "<belegt>",
      "ende_benutzt": "<ende_benutzt>",
      "wegraeumen_min": "<wegraeumen_min>",
      "pruefen_min": "<pruefen_min>",
      "sauber_ab": "<sauber_ab>",
      "separate_ablage": "<separate_ablage>"
    },
    "name": "pflegeablage_sauber_schmutzig_nacheinander"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegtYesSind Trennung, Aufstellort und Umstellablauf für die Teile belegt?
sauber_abYesTagesminute, zu der die sauberen Teile eingeplant sind.
pruefen_minYesZeit für den vorgesehenen Prüfschritt der leeren Ablage.
ende_benutztYesTagesminute, zu der die benutzten Teile weg können.
wegraeumen_minYesBeobachtete Dauer bis diese Teile getrennt abgelegt sind.
separate_ablageYesIst eine bestätigte, davon unabhängige saubere Ablage frei?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 that the workplace is shared and that the clearing duration must be observed (i.e., measured, not estimated), which is genuinely useful context. However, it does not resolve the tension between the mutating German verb and the read-only hint, nor does it describe what the check evaluates.

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 description is short and front-loads the operation, but the German and English sentences are near-duplicate restatements rather than complementary information, so a chunk of the text earns little. Neither sentence explains the sequential ordering rule the parameters encode.

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?

This is a six-required-parameter, no-output-schema tool, so the description carries the burden of explaining what the check produces and under what ordering constraints. It does neither: an agent cannot tell from the text whether the result is a feasibility verdict, a schedule, or a validation of the stored/incoming items.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: every parameter, including the two booleans (belegt, separate_ablage) and the four day-minute values, is documented in the schema itself. With no enum or nested structures to explain, the description is not obligated to add parameter meaning; the only small gap is that it does not explain how ende_benutzt and wegraeumen_min interact to form the sequential window.

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 English half states a verb and resource ("Check a sequential switch between used and clean work materials"), but the German half uses "umstellen" (reconfigure/switch over), which reads as a mutation and muddies what the tool actually does. It is not obvious from the description whether the tool computes/schedules a switch or merely validates feasibility, and nothing distinguishes it from the many sibling planning tools.

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 when-to-use or when-not-to-use guidance, no prerequisites beyond the vague hint at an "observed" clearing duration, and no alternative tool named despite a dense sibling catalog. The agent must infer the triggering situation entirely from the name.

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