Skip to main content
Glama

scobees_upload_material

Upload a local file to a task as learning material or a sample solution, and optionally replace an existing attachment after the upload succeeds.

Instructions

Hängt eine lokale Datei an eine Aufgabe an – als Material (PDF, Bild, HTML-Simulation, interaktive Seite, GeoGebra-Datei …) oder als Musterlösung. ersetzt_attachment_id: nach erfolgreichem Hochladen wird dieser alte Anhang gelöscht (z. B. bei einer neuen Fassung derselben Datei); schlägt der Upload fehl, bleibt der alte unangetastet.

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": {
      "aufgabe_id": "<aufgabe_id>",
      "file_path": "<file_path>"
    },
    "name": "scobees_upload_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsoluter lokaler Pfad
aufgabe_idYes
als_musterloesungNo
ersetzt_attachment_idNoATT-ID eines bestehenden Anhangs/einer Musterlösung an derselben Aufgabe, der nach erfolgreichem Upload gelöscht wird (aus scobees_get_aufgabe)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.10
    • addedInput schema / properties / ersetzt_attachment_id
      Added value: +{
      +  "description": "ATT-ID eines bestehenden Anhangs/einer Musterlösung an derselben Aufgabe, der nach erfolgreichem Upload gelöscht wird (aus scobees_get_aufgabe)",
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuinely useful trait: the replacement attachment is deleted only after a successful upload and left untouched on failure, which is real transactional semantics. It omits format/size limits, permission or auth requirements, and what happens to the uploaded file on failure.

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 core action, and the type enumeration is compact. The trailing ellipsis-style list ('…') is slightly loose but does not obscure the meaning; nothing is redundant.

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 4-parameter mutation with no annotations and no output schema, the definition covers the replacement semantics well. It leaves gaps an agent would want: whether an attachment ID is returned (needed to later pass as ersetzt_attachment_id), supported format/size constraints, and any authorization requirements.

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

Parameters4/5

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

Schema coverage is 50%, and the description compensates well for the highest-risk parameter: ersetzt_attachment_id is explained beyond the schema with its success/failure deletion behavior and the concrete 'same file, new version' use case. als_musterloesung is also glossed by 'oder als Musterlösung'; only aufgabe_id gets no added meaning, though it is largely self-evident.

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?

Names a concrete verb (anhängen) and resource (lokale Datei an eine Aufgabe) and enumerates accepted material types plus the Musterlösung variant. It does not differentiate itself from close siblings such as scobees_upload_bild or scobees_delete_material, and listing 'Bild' as a material type could leave an agent unsure which upload tool to pick for images.

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?

The description makes clear this is the path for attaching material or a model solution to an existing Aufgabe, and the ersetzt_attachment_id clause hints at the update-an-existing-attachment scenario. However, there is no explicit when-not guidance, no mention of prerequisites (does the Aufgabe need to exist, does the user need rights), and no routing advice versus scobees_upload_bild.

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