Skip to main content
Glama

scobees_get_lernpfad

Loads a learning path's full outline-to-task tree with IDs required for edits and root assignment status showing whether learners already see changes.

Instructions

Lädt einen Lernpfad mit vollständigem Aufbau (Gliederungen → Aufgaben) als kompakten Baum. IDs daraus werden für Änderungen benötigt. An der Wurzel steht zugewiesen (true = Lernende arbeiten bereits damit, jede Änderung ist für sie sofort sichtbar). Je Element: typ, Status, hat_titelbild (eigenes Kachelbild gesetzt?), bei Aufgaben zusätzlich Art-Kennung, Anhänge und Arbeitsblatt-Bausteine. Die Beschreibung der Lernpfad-Wurzel kommt unverändert zurück.

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

Input Schema

NameRequiredDescriptionDefault
idYesLernpfad-ID (LI-…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it delivers meaningful behavioral context: the result is a compact tree, the root carries a "zugewiesen" flag whose true value means every change is immediately visible to learners, and the root's own description is returned verbatim. What remains unsaid is failure behavior (invalid or foreign ID) and whether 'kompakt' implies truncation of nested content.

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?

Four sentences, each carrying new information: what is returned, why it matters (IDs for changes), the root's visibility flag, and the per-element field list. It is front-loaded with the payload description, with only minor density cost from the parenthetical glosses.

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?

This is a read tool with no output schema, so the description must describe return shape, and it does: a tree of Gliederungen and Aufgaben, per-element typ/Status/hat_titelbild, plus Art-Kennung, Anhänge and Arbeitsblatt-Bausteine for tasks. Missing are edge cases such as how deep the tree goes for a nested Wahlpflicht and what an error response looks like, but the essential contract is covered.

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?

There is a single parameter, id, and the schema already documents it at 100% coverage including the LI-… format. The description adds no further meaning about that parameter (no scope, no ownership or permission implications), so the baseline of 3 applies rather than a higher score.

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 names a specific verb and resource ("Lädt einen Lernpfad") and its scope ("mit vollständigem Aufbau (Gliederungen → Aufgaben) als kompakten Baum"), so the agent knows this returns a whole structure, not a flat record. It does not explicitly contrast itself with scobees_list_lernpfade or scobees_get_aufgabe, but the 'full tree' framing makes the distinction inferable.

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?

One workflow hint is present: "IDs daraus werden für Änderungen benötigt", which tells the agent to call this before any update/move/patch operation. Beyond that, there is no explicit when-to-use or when-not, and no named alternative for the single-task case (scobees_get_aufgabe) or the browse case (scobees_list_lernpfade).

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