Skip to main content
Glama

scobees_update_aufgabe

Updates an existing task by changing only the supplied fields, preserving its cover image; worksheet content is replaced only when explicitly provided.

Instructions

Ändert eine bestehende Aufgabe. Nur übergebene Felder werden geändert; ein vorhandenes Kachelbild bleibt erhalten. arbeitsblatt_markdown/serlo_json ersetzen das Arbeitsblatt komplett (vorher mit scobees_get_aufgabe lesen) – für einzelne Textstellen ist scobees_patch_arbeitsblatt der kürzere und sicherere Weg.

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>"
    },
    "name": "scobees_update_aufgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
artNo
nameNo
linksNo
serlo_jsonNo
aufgabentypNo
abgabeformenNo
interne_notizNo
estimated_timeNo
cover_image_pathNoLokaler Pfad zu einem Kachelbild (PNG oder JPG; live geprüft mit PNG bis 1,3 MB). Quadratisch anlegen – scobees beschneidet die Kachel quadratisch – und ein Motiv wählen, das klein noch erkennbar ist.
description_htmlNo
differenzierungenNoSiehe scobees_create_aufgabe: leer trägt alle aktuellen Niveaus explizit ein, das ist kein Fehler.
arbeitsblatt_markdownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.10
    • addedInput schema / properties / cover_image_path
      Added value: +{
      +  "description": "Lokaler Pfad zu einem Kachelbild (PNG oder JPG; live geprüft mit PNG bis 1,3 MB). Quadratisch anlegen – scobees beschneidet die Kachel quadratisch – und ein Motiv wählen, das klein noch erkennbar ist.",
      +  "type": "string"
      +}
    • addedInput schema / properties / differenzierungen / description
      Added value: +"Siehe scobees_create_aufgabe: leer trägt alle aktuellen Niveaus explizit ein, das ist kein Fehler."
  2. Changed3 schema fields changedv0.1.4
    • addedInput schema / properties / abgabeformen
      Added value: +{
      +  "items": {
      +    "enum": [
      +      "file",
      +      "pen",
      +      "link"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / art / enum
      Previous value: -[
      -  "info",
      -  "selbstkontrolle",
      -  "abgabe_optional",
      -  "abgabe_pflicht",
      -  "abgabe_optional_sc"
      -]New value: +[
      +  "info",
      +  "selbstkontrolle",
      +  "abgabe_optional",
      +  "abgabe_pflicht",
      +  "abgabe_selbstkorrektur",
      +  "abgabe_pflicht_selbstkorrektur"
      +]
    • addedInput schema / properties / aufgabentyp
      Added value: +{
      +  "enum": [
      +    "pflicht",
      +    "extra",
      +    "training",
      +    "info"
      +  ],
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and it delivers the non-obvious parts: partial-update semantics, that an existing Kachelbild survives unless cover_image_path is supplied, and that arbeitsblatt_markdown/serlo_json overwrite the whole worksheet rather than merging. It stops short of permissions, behavior when id does not exist, or whether omitted-vs-null differ.

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 tightly packed sentences, front-loaded with the core action before the replacement warning and the sibling pointer. No filler, though the long parenthetical makes the second half harder to scan than it needs to be.

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?

For a 13-parameter mutation tool with no annotations and no output schema, the description covers behavior well but leaves most field-level meaning undocumented, which is the larger risk here. An agent can invoke it, but can easily set the wrong enum value or mangle links/abgabeformen.

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

Parameters2/5

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

With 13 parameters and only 15% schema description coverage, the description is expected to compensate, but it only illuminates three of them (cover_image_path, arbeitsblatt_markdown, serlo_json) plus the generic partial-update rule. The six-value art enum, aufgabentyp, abgabeformen, links, interne_notiz, estimated_time and description_html get nothing beyond their names.

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?

"Ändert eine bestehende Aufgabe" names a specific verb and resource, and the very next clause pins down the update mode (patch-style, only supplied fields change). It also names the two sibling tools that serve adjacent purposes (scobees_get_aufgabe, scobees_patch_arbeitsblatt), so an agent can place it without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: read the worksheet with scobees_get_aufgabe before replacing it, and use scobees_patch_arbeitsblatt for edits to individual text passages instead of this tool. That is a genuine when-to-use / when-not-to-use / alternative statement, not an implied one.

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