Skip to main content
Glama

scobees_move

Move a task, outline, or elective to a new position, including into another outline of the same learning path; it can also convert a single task into an elective subtask.

Instructions

Verschiebt eine Aufgabe/Gliederung/Wahlpflicht an eine Position (sort_order, 0-basiert) – auch in eine andere Gliederung desselben Lernpfads. Eine einzelne Aufgabe lässt sich auch in eine Wahlpflichtaufgabe verschieben (ab scobees 94.6): Sie wird dabei zur Unteraufgabe, verliert ihren bisherigen Aufgabentyp (Pflicht/Extra/Training/Projekt) und kommt nicht wieder heraus – das Ergebnis nennt die Umstellung unter warnung. Unteraufgaben lassen sich nur innerhalb ihrer Wahlpflichtaufgabe umsortieren.

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>",
      "parent_id": "<parent_id>",
      "sort_order": "<sort_order>"
    },
    "name": "scobees_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
parent_idYesZiel: Gliederung, Lernpfad oder (nur für einzelne Aufgaben) Wahlpflichtaufgabe
sort_orderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.10
    • changedInput schema / properties / parent_id / description
      Previous value: -"Ziel-Gliederung/-Lernpfad"New value: +"Ziel: Gliederung, Lernpfad oder (nur für einzelne Aufgaben) Wahlpflichtaufgabe"
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so the description must carry the whole behavioral burden, and it does disclose the most consequential trait: the move into a Wahlpflicht is type-destroying and irreversible ("verliert ihren bisherigen Aufgabentyp ... kommt nicht wieder heraus") and is surfaced under a "warnung" key in the result. It says nothing about required permissions, whether repeated identical moves are idempotent, or failure behavior for invalid sort_order ranges.

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?

Front-loaded with the core action and the indexing convention, then layered with the exception case. The final sentence on Unteraufgaben is a necessary constraint rather than filler, though the long German sentence chains could be split for faster scanning.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the move semantics, the cross-container scope, the irreversible conversion side effect, and the result's warning field – enough to call it correctly. Only auth/permission expectations and error conditions remain unstated.

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 only 33% (only parent_id is annotated), so the description has to compensate and largely does: it defines sort_order as 0-based positioning and clarifies which entity kinds id and parent_id may refer to, including the Wahlpflicht target restriction. It still does not say what happens when sort_order exceeds the current child count or whether negative/large values are clamped.

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?

States a concrete verb ("Verschiebt") with three named resource types (Aufgabe/Gliederung/Wahlpflicht) and the target concept (Position, sort_order, 0-basiert), plus the cross-Gliederung scope. An agent can distinguish this from update/create siblings without opening any other tool definition.

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?

Gives the operative conditions: repositioning within a Lernpfad, moving into another Gliederung of the same Lernpfad, and the special case of moving a single Aufgabe into a Wahlpflichtaufgabe (ab 94.6). It also states a hard exclusion – Unteraufgaben can only be reordered inside their own Wahlpflichtaufgabe – but never names a sibling tool as the alternative for other kinds of change.

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