Skip to main content
Glama

scobees_update_lernpfad

Updates an existing learning path's subject, name, description, year groups, keywords, cover image, solve order, and school-library visibility while preserving fields you do not specify.

Instructions

Ändert einen bestehenden Lernpfad (Wurzel): Fach, Name, Beschreibung, Jahrgänge, Stichwörter, Titelbild, Reihenfolge. Nicht angegebene Felder bleiben erhalten. in_bib: Schalter „In schuleigener Bib veröffentlichen“. Fach bleibt beim Administrator, Zuweisung an Lerngruppen in der Weboberfläche.

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_lernpfad"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLI-ID des Lernpfads
nameNo
in_bibNoIn schuleigener Bib veröffentlichen (true/false)
jahrgaengeNo
subject_idNoLernpfad in ein anderes Fach verschieben (Fach-ID aus scobees_list_subjects). Achtung: Lernende brauchen im Fach des Pfads ein Niveau, sonst ist keine Zuweisung möglich.
descriptionNoBeschreibung als reiner Text – scobees zeigt sie hier nicht als HTML gerendert, mitgeschicktes HTML würde als sichtbarer Tag-Text erscheinen und wird deshalb automatisch entfernt.
solve_orderNo
stichwoerterNo
cover_image_pathNoNeues Titelbild (lokaler Pfad), optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.10
    • addedInput schema / properties / description / description
      Added value: +"Beschreibung als reiner Text – scobees zeigt sie hier nicht als HTML gerendert, mitgeschicktes HTML würde als sichtbarer Tag-Text erscheinen und wird deshalb automatisch entfernt."
  2. Changed2 schema fields changedv0.1.4
    • changedInput schema / properties / solve_order / enum
      Previous value: -[
      -  "none",
      -  "after_solving"
      -]New value: +[
      +  "none",
      +  "after_solving",
      +  "after_selfcorrection",
      +  "after_teacher_correction"
      +]
    • addedInput schema / properties / subject_id
      Added value: +{
      +  "description": "Lernpfad in ein anderes Fach verschieben (Fach-ID aus scobees_list_subjects). Achtung: Lernende brauchen im Fach des Pfads ein Niveau, sonst ist keine Zuweisung möglich.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses partial-update semantics and that HTML in the description is stripped, but the stripping detail is already in the schema, and it omits permissions, whether array fields (jahrgaenge, stichwoerter) are replaced wholesale, and the response shape. The closing sentence about Fach/administration is ambiguous rather than clarifying.

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 verb and resource, then the field list, then caveats; no filler. The final sentence about Fach and Lerngruppen reads as a compressed afterthought whose meaning is not fully clear.

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

Completeness3/5

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

For a 9-parameter mutation tool with no annotations and no output schema, the description covers the essentials of partial updates and the HTML constraint, but leaves permissions, replacement semantics for list fields, and error/return behavior unaddressed.

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?

Schema coverage is 56%, so the description must compensate. It maps several properties to plain-language labels ("Reihenfolge" for solve_order, "Titelbild" for cover_image_path) and repeats the in_bib and subject caveats, but it does not explain the meaning of the solve_order enum values or the optionality of the remaining fields.

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

Purpose4/5

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

States a specific verb ("Ändert") and resource ("bestehenden Lernpfad (Wurzel)") and enumerates the editable fields, which distinguishes it from the sibling create_lernpfad. It does not explicitly name the create/get siblings, so the differentiation relies on the word "bestehenden".

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

Usage Guidelines3/5

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

Says edits are partial ("Nicht angegebene Felder bleiben erhalten") and notes that Lerngruppen assignment happens in the web UI rather than here, which implicitly scopes the tool. It never explicitly says when to prefer create_lernpfad or which preconditions (ownership, admin role for Fach) must hold before calling.

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