Skip to main content
Glama

scobees_create_wahlpflicht

Create a compulsory-elective assignment container that requires learners to complete a minimum number of subtasks, then add subtasks under its parent ID.

Instructions

Legt eine Wahlpflichtaufgabe an: ein Container, aus dem Lernende eine Mindestanzahl an Unteraufgaben lösen. Unteraufgaben danach mit scobees_create_aufgabe (parent_id = diese ID) anlegen. Eine bestehende Aufgabe lässt sich ab scobees 94.6 auch mit scobees_move hineinschieben (sie verliert dabei ihren Aufgabentyp); heraus kommt eine Unteraufgabe nicht mehr.

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": {
      "parent_id": "<parent_id>",
      "name": "<name>"
    },
    "name": "scobees_create_wahlpflicht"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNoHex-Farbe#c88503
parent_idYes
cover_image_pathNoLokales Titelbild, optional
description_htmlNo
mindest_aufgabenNoWie viele Unteraufgaben müssen gelöst werden

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that moving a task in strips its original task type, that a subtask can never be moved back out, and that the move capability requires at least version 94.6. It does not mention permissions, whether name/color collisions are handled, or what the call returns, so it stops short of full transparency.

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?

Three tight sentences with no filler, and the core definition is front-loaded before the workflow and version caveats. Slightly dense phrasing in the third sentence (the parenthetical about losing task type) costs a small amount of readability but nothing is wasted.

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 creation tool with no output schema and no annotations, the definition covers the entity's meaning, the required follow-up call, and the irreversible-move caveat — all the decision-relevant facts. It does not state what the call returns (the new container ID is only implied by "diese ID"), which is the remaining gap.

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?

The container concept implicitly explains the mindest_aufgaben parameter (how many subtasks must be solved), and the parent_id note clarifies how the returned ID is reused downstream. But three parameters (color, cover_image_path, description_html) get no coverage in the description and only partial schema descriptions, leaving half the surface undocumented — a baseline 3 rather than genuine added value.

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 specific verb ("Legt ... an") and resource ("Wahlpflichtaufgabe") and then defines what that resource actually is: a container from which learners solve a minimum number of subtasks. That definition alone distinguishes it from sibling scobees_create_aufgabe, which creates the individual subtasks inside it.

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 explicit follow-up workflow — create subtasks afterwards via scobees_create_aufgabe with parent_id set to this new ID — and names scobees_move as the route for pulling an existing task in. What is missing is guidance for when to choose this container over other structural siblings like scobees_create_lernpfad or scobees_create_gliederung; only the create_aufgabe/move relationships are covered.

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