PLATO MCP

submit_assignment

Destructive

Submit text and/or file attachments for an assignment. IRREVERSIBLE once dry_run=False.

    Call with dry_run=True (default) first, show the preview to the user, and
    only call again with dry_run=False (same parameters) after they explicitly
    confirm. Provide text, file_paths/file_contents, or both -- whichever this
    assignment actually accepts (see get_assignment_detail).

    file_paths works only when this server is running locally (stdio, e.g.
    Claude Code/Desktop) -- rejected with a clear error over a remote
    (streamable-http, e.g. a Claude.ai Connector) connection, mirroring
    download_course_file's own stdio-vs-remote split. file_contents works
    over either transport and is the only option remotely, since this
    server's disk is not reachable by you there.

Input Schema

Name	Required	Description
`text`	No	Plain-text submission content. Omit (empty string) for a file-only submission. Rejected if this assignment doesn't accept online text -- check get_assignment_detail's onlinetext_submission.enabled first.
`dry_run`	No	If True (default), only preview the submission without sending it. Call again with dry_run=False (same parameters) to actually submit it.
`course_id`	Yes	PLATO/Moodle numeric course id, e.g. from list_courses.
`file_paths`	No	Local filesystem paths to upload as file attachments. Only works when this server is running locally (stdio) -- rejected with a clear error over a remote/streamable-http connection (use file_contents there instead). Rejected if this assignment doesn't accept file submissions, exceeds its max file count/size, or uses a disallowed extension -- check get_assignment_detail's file_submission (enabled/max_files/max_size_bytes/allowed_extensions) first.
`assignment_id`	Yes	Assignment id, e.g. from list_assignments.
`file_contents`	No	File attachments as {filename, content_base64} -- works over either transport, and is the only way to attach files when this server is running remotely (streamable-http), since it has no local filesystem to read a path from there. Each file is capped at 5MB decoded, in addition to this assignment's own max file count/size/extension rules (see get_assignment_detail's file_submission).

Output Schema

Name	Required	Description	Default
`dry_run`	Yes
`message`	Yes
`preview`	Yes
`executed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency. The description reinforces this with the exact consequence (IRREVERSIBLE once dry_run=False), the safe preview default, and transport-specific rejection behavior, adding substantial operational context beyond the annotations.

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?

The description is reasonably sized and front-loads the most critical warning. It is somewhat repetitive of schema details around file_paths and file_contents, but the repetition supports the destructive workflow and the structure remains clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a destructive submission tool with an output schema, the description covers everything an agent needs: irreversible action warning, dry-run confirmation flow, accepted submission modes, transport constraints, and where to check assignment-specific rules. Return values need not be explained because an output schema exists.

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 the schema already documents each parameter in depth. The description reinforces the same constraints, especially the local-only nature of file_paths and remote-compatible file_contents, but adds little syntax or meaning beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: submitting text and/or file attachments for an assignment. It is immediately distinguishable from sibling tools like remove_submission, and the irreversible final action is front-loaded.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit two-step workflow: call with dry_run=True first, show the preview, obtain explicit confirmation, then call again with dry_run=False using the same parameters. It also tells the agent to consult get_assignment_detail to determine which submission types the assignment accepts and explains the transport-dependent choice between file_paths and file_contents.

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

All PLATO MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.