Skip to main content
Glama

scobees_delete_material

Deletes one attachment, such as material or a sample solution, from a task after verifying it belongs to that task; requires confirm=true and warns when removing the last PDF for pen submissions.

Instructions

Löscht genau einen Anhang (Material oder Musterlösung) einer Aufgabe. attachment_id aus scobees_get_aufgabe (anhaenge[].id / musterloesungen[].id). Erfordert confirm=true. Prüft, dass der Anhang wirklich zu dieser Aufgabe gehört, und warnt, wenn es das letzte PDF einer Stift-Abgabe (abgabeformen: pen) ist – ohne PDF ist dort kein Abgeben mehr möglich.

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>",
      "attachment_id": "<attachment_id>",
      "confirm": "<confirm>"
    },
    "name": "scobees_delete_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMuss true sein
aufgabe_idYes
attachment_idYesATT-ID des zu löschenden Anhangs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.10

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does real work: it discloses a server-side ownership check (the attachment must belong to this Aufgabe) and a specific edge-case warning about deleting the last PDF of a pen submission (abgabeformen: pen). What it omits is whether deletion is permanent/irreversible and what the response contains, which matters for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the action and scope, then the ID provenance, then the guardrails. Every clause carries distinct information with no repetition.

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 destructive tool with no annotations and no output schema, this is nearly complete: scope, ID sourcing, confirmation gate, ownership validation and a concrete data-loss warning are all present. Only irreversibility and the expected return/error shape are left unstated.

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 67%, and the description compensates by explaining that attachment_id is an ATT-ID sourced from specific nested fields of scobees_get_aufgabe, plus the confirm=true gate. aufgabe_id gets no explanation in either the schema or the description, leaving one parameter's semantics implicit.

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 gives a specific verb (löscht), a precisely scoped resource (genau einen Anhang – Material oder Musterlösung – einer Aufgabe) and cardinality, so the agent knows this is a single-attachment delete rather than a generic delete. The parenthetical naming both attachment kinds removes ambiguity about what counts as an 'Anhang'.

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 explicitly tells the agent where the attachment_id comes from (scobees_get_aufgabe, anhaenge[].id / musterloesungen[].id) and that confirm=true is mandatory, which is strong pre-call guidance. It never states when NOT to use it or points to scobees_delete as the alternative for other objects, so it stops short of full routing guidance.

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