Skip to main content
Glama

learnjcu_submit

Destructive

Submit files and optional text to a LearnJCU Ultra assignment as a new attempt; validate with a dry run and confirm before sending.

Instructions

Submit files (and optional text) to a LearnJCU Ultra assignment as a new attempt. Course staff see it at once, and it may count as your graded attempt. Use when the user asks to submit an assignment on LearnJCU. If the item links to an external tool, submit there instead. Always call with dryRun: true first, show the plan, and wait for the user to confirm.

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": {
      "courseId": "<courseId>",
      "assignment": "<assignment>"
    },
    "name": "learnjcu_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to put in the submission box
filesNoAbsolute paths of the files to upload
dryRunNoValidate and return the plan without sending
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.
confirmNoMust be true to actually send. Only set it after showing the user the dryRun plan and getting their explicit yes.
courseIdYesCourse primary id like "_123456_1" (from learnjcu_list_courses), a subject code like "BU2001", or the full course code
assignmentYesA unique part of the assignment title (e.g. "CW2"), or its content or gradebook column id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds consequences the schema cannot express: staff see the submission immediately and it may count as the graded attempt, so the action is effectively irreversible in academic terms. It also prescribes the dryRun/confirm safety gate, which is meaningful behavioral context beyond the hints.

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?

Four short sentences, front-loaded with the action and consequence before the routing rule and the procedural mandate. No sentence is redundant and nothing repeats the schema verbatim.

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 7-parameter destructive mutation with no output schema, the definition covers consequences, the alternative path, and the confirmation protocol. It is silent on what the dryRun plan actually contains and on what happens when an attempt already exists, which are the remaining gaps an agent might hit.

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 100%, so per-parameter meaning is already documented; the description still adds workflow semantics the schema only hints at by mandating 'Always call with dryRun: true first' and tying confirm to an explicit user yes. It adds little about the file/text semantics themselves, so it sits above the baseline 3 but not at the top.

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 opening sentence gives a specific verb and resource ('Submit files (and optional text) to a LearnJCU Ultra assignment') plus a scope qualifier ('as a new attempt'), which separates it cleanly from learnjcu_list_submissions and the read-only content tools in the sibling set.

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 states the triggering condition ('Use when the user asks to submit an assignment on LearnJCU'), an explicit exclusion with redirect ('If the item links to an external tool, submit there instead'), and a mandatory two-step protocol (dryRun first, show plan, wait for confirmation). That is when-to-use, when-not-to-use, and a required call sequence.

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