Skip to main content
Glama

scobees_delete

Deletes tasks, empty outlines or elective tasks, and whole learning paths after confirmation; use the assigned-path flag only with teacher approval for individual tasks in active paths.

Instructions

Löscht eine Aufgabe, eine leere Gliederung oder Wahlpflichtaufgabe oder einen ganzen Lernpfad. Erfordert confirm=true. Regeln von scobees: Ein ganzer Lernpfad wird mit allen Unterelementen gelöscht, aber nur solange er niemandem zugewiesen ist. Gliederungen und Wahlpflichtaufgaben lassen sich nur leer löschen (erst die Aufgaben darin löschen). Einzelne Aufgaben lassen sich auch in einem zugewiesenen Lernpfad löschen und verschwinden dann sofort bei den Lernenden, auch wenn schon Lernergebnisse abgegeben wurden – deshalb verlangt das Werkzeug dort zusätzlich auch_wenn_zugewiesen=true.

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": {
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "scobees_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmYesMuss true sein
auch_wenn_zugewiesenNoNur nach ausdrücklicher Zustimmung der Lehrkraft: Löschen in einem Lernpfad erlauben, mit dem Lernende bereits arbeiten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.13
    • addedInput schema / properties / auch_wenn_zugewiesen
      Added value: +{
      +  "description": "Nur nach ausdrücklicher Zustimmung der Lehrkraft: Löschen in einem Lernpfad erlauben, mit dem Lernende bereits arbeiten",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it discloses cascade deletion of all subelements, the hard precondition of being unassigned, the confirm=true requirement, and the consequence that deleted Aufgaben vanish immediately for learners even when results were already submitted.

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?

Purpose and the confirm requirement are front-loaded, then rules follow in a logical order. The block is dense but nearly every clause carries a distinct rule; the long final sentence could be split for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive three-parameter tool with no annotations and no output schema, the guidance on what can be deleted and under which conditions is unusually complete. Remaining gaps are minor: no statement of what is returned on success/failure, no clarification of the 'id' format or whether it is type-specific.

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 coverage is 67%, with confirm and auch_wenn_zugewiesen already documented in the schema. The description adds real meaning beyond that: it explains why the override flag exists (immediate disappearance for learners, submitted results) and that it requires explicit teacher consent, though the 'id' parameter receives no explanation anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb ('Löscht') and enumerates the exact resource types affected: Aufgabe, leere Gliederung, Wahlpflichtaufgabe, ganzer Lernpfad. That enumeration also implicitly separates it from the material-deletion sibling, since materials are not among the listed targets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states concrete preconditions and exclusions: a Lernpfad is deleted with all children only while unassigned, Gliederungen/Wahlpflichtaufgaben only when empty, and single Aufgaben only in an assigned path with auch_wenn_zugewiesen=true. What it lacks is any explicit naming of an alternative tool (e.g. how to remove an assigned path, or the material-deletion sibling).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.