Skip to main content
Glama

scobees_get_aufgabe

Retrieve a single assignment’s worksheet, submission options, links, attachments, sample solutions with ATT IDs, and tile image before modifying an existing assignment.

Instructions

Lädt eine einzelne Aufgabe: Arbeitsblatt als Markdown, Abgabeform (art, abgabeformen), Links, Anhänge und Musterlösungen mit ihren ATT-IDs (für scobees_delete_material / ersetzt_attachment_id), Kachelbild. Vor jeder Änderung an einer bestehenden Aufgabe aufrufen.

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

Input Schema

NameRequiredDescriptionDefault
idYesAufgaben-ID (LI-…)
mit_serlo_jsonNozusätzlich das rohe Serlo-JSON ausgeben

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/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 does disclose the content of the returned payload in useful detail, including the ATT-IDs needed for later mutations. It says nothing about authorization requirements, behavior when the id does not exist, or the size and format of embedded attachments and images. The description is helpful, but incomplete for a tool with zero annotation coverage.

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?

It is front-loaded with the verb and resource, then a dense enumeration, then a one-line imperative, which is a good structure. The enumeration is long and packs several concepts into a single sentence, but almost every item earns its place by telling the agent what it can extract.

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?

With no annotations, no output schema, and only two parameters, the description does the heavy lifting by enumerating the returned fields and stating the workflow precondition. Gaps remain around error behavior and whether mit_serlo_json alters the listed fields, but nothing essential for calling it correctly is absent. It is largely complete for its complexity.

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 description coverage is 100%, so both id (LI-…) and mit_serlo_json are already documented in the schema. The description never explains what mit_serlo_json changes about the response, though it does tie the returned ATT-IDs to downstream tools. The baseline 3 applies when the schema already does the work.

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?

The description opens with a concrete verb and resource, "Lädt eine einzelne Aufgabe", and then enumerates exactly what that single record contains: Arbeitsblatt als Markdown, Abgabeform, Links, Anhänge, Musterlösungen mit ATT-IDs und Kachelbild. That level of detail distinguishes it from list- or path-oriented siblings such as scobees_get_lernpfad or scobees_list_lernpfade.

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?

It gives an explicit workflow precondition with "Vor jeder Änderung an einer bestehenden Aufgabe aufrufen", so an agent knows the read-before-write pattern relative to scobees_update_aufgabe. It also names where the returned ATT-IDs feed into scobees_delete_material and ersetzt_attachment_id. What it lacks is any exclusion, that is when not to call it, so it falls short of a full 5.

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