Skip to main content
Glama

scobees_update_gliederung

Update an outline structure's name, description, cover image, color, or task solve order; unspecified fields stay unchanged.

Instructions

Ändert Name, Beschreibung, Kachelbild, Farbe und/oder Bearbeitungsreihenfolge (solve_order) einer Gliederungsstruktur. Nicht angegebene Felder bleiben erhalten (auch ein vorhandenes Kachelbild, die Farbe und die Reihenfolge).

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

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
colorNoHex-Farbe der Gliederung
solve_orderNoBearbeitungsreihenfolge der Aufgaben in dieser Gliederung: none = frei (Standard); after_solving = nach Reihenfolge; after_selfcorrection = nach Selbstkorrektur; after_teacher_correction = nach Korrektur durch die Lehrkraft
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.13
    • addedInput schema / properties / solve_order
      Added value: +{
      +  "description": "Bearbeitungsreihenfolge der Aufgaben in dieser Gliederung: none = frei (Standard); after_solving = nach Reihenfolge; after_selfcorrection = nach Selbstkorrektur; after_teacher_correction = nach Korrektur durch die Lehrkraft",
      +  "enum": [
      +    "none",
      +    "after_solving",
      +    "after_selfcorrection",
      +    "after_teacher_correction"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv0.1.10
    • addedInput schema / properties / color
      Added value: +{
      +  "description": "Hex-Farbe der Gliederung",
      +  "type": "string"
      +}
    • 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"
      +}
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key behavioral trait: unspecified fields are preserved, explicitly including an existing cover image, color and ordering — valuable patch semantics that prevent accidental data loss. It does not disclose what happens on an invalid id, whether changes are reversible, permission requirements, or what the call returns.

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?

Two sentences, front-loaded with the mutable field list followed immediately by the patch guarantee. The parenthetical repeating cover image, color and order is slightly redundant with "Nicht angegebene Felder bleiben erhalten", but it targets the fields an agent is most likely to fear clobbering.

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 6-parameter, one-required partial-update tool with no annotations and no output schema, the description covers the essential semantic risk (field preservation) and the field set. Remaining gaps — identifier requirement, error behavior, return shape, and permissions — are real but modest for a straightforward update call.

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 50%, and the description at least confirms which fields are updatable and maps "Beschreibung" to description_html and "Bearbeitungsreihenfolge" to solve_order. However, it adds no format detail for name or description_html and never states that id is the required identifier of the target structure, so it only partially compensates for the undocumented half of the schema.

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?

The description uses a specific verb ("Ändert") plus an enumerated list of the mutable fields and names the resource ("Gliederungsstruktur"), which separates it from siblings such as scobees_update_aufgabe and scobees_update_lernpfad. It stops short of explicitly naming create_gliederung as the non-update alternative, but the resource scope is unambiguous.

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?

Usage is implied rather than stated: the reader infers this is the tool for modifying an existing Gliederung and that partial updates are allowed. There is no explicit when-to-use/when-not guidance versus scobees_create_gliederung, and no mention of required permissions or preconditions (e.g. that the Gliederung must already exist).

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