moodle-um

moodle_remove_submission

Remove an assignment submission to undo an accidental upload; this action is irreversible and requires explicit confirmation.

Instructions

Remove your submission for an assignment. IRREVERSIBLE.

Use this to undo an accidental submission. Requires explicit user confirmation (confirm=true).

Args: cmid: course-module id of the assignment. confirm: must be true.

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": {
      "cmid": "<cmid>"
    },
    "name": "moodle_remove_submission"
  }
}

Input Schema

Name	Required	Description	Default
`cmid`	Yes
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 12, 2026

TDQS

A4.3/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 the important part: it flags IRREVERSIBLE in caps, names what is destroyed (your submission), and states that explicit user confirmation is required via confirm=true. It leaves open whether the assignment can be re-submitted afterwards or how grades are affected, which are the next questions an agent would have.

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?

Front-loaded and compact: the destructive warning is in sentence one, usage in sentence two, then a tight two-line arg list. The "Args:" block is slightly documentation-format boilerplate but each line adds real information.

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 two-parameter destructive tool with no annotations and no output schema, the description covers the essentials: irreversible effect, confirmation gate, and both parameters. Only the post-removal state (can the student resubmit, what is returned) is unaddressed.

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 0% and the schema only supplies bare titles ("Cmid", "Confirm"), so the description is the sole source of meaning: cmid is the course-module id of the assignment, and confirm must be set true despite defaulting to false. It does not say where an agent obtains a course-module id, which keeps this from a 5.

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?

States a specific verb and resource ("Remove your submission for an assignment") and immediately scopes it as the undo path for an accidental submission, which separates it from moodle_submit_assignment without needing the schema.

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?

"Use this to undo an accidental submission" gives an explicit when-to-use condition, and the confirm=true prerequisite is spelled out in both prose and args. It stops short of naming a when-not condition or pointing to a sibling (e.g. re-submitting via moodle_submit_assignment after removal).

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