Cubite LMS: Learning Management System

Bulk enroll learners

enrollment_bulk_create

Enroll up to 100 learners in one course in a single call, under the same rules as enrollment_create (accounts found or created, prerequisites checked unless skipped, no email unless sendInvite:true); use enrollment_create for one learner or to pass redirectTo or externalReference. Learners are processed one at a time: an invalid email or unmet prerequisites fails only that learner, so the call can partly succeed, but an unexpected server error stops the batch with no per-learner results (learners enrolled before it stay enrolled, so re-run the call). Already-enrolled learners keep their enrollment (created:false, status label reset to "completed"), so a retry duplicates nothing, though it re-sends invites when sendInvite is on and replaces earlier sign-in links. Returns "Enrolled N, failed M" and a result per learner (email, ok, created, emailSent, magicLinkUrl, enrollment; or error and missingPrerequisites); if every learner fails, the call errors with those results. Get course ids from course_list.

Input Schema

TableJSON Schema

Name	Required	Description
`emails`	No	Learner emails, 1 to 100. Use this OR learners.
`courseId`	Yes	Id of a course on this site (required). For a course linked to Open edX this creates only Cubite enrollments, not the learners' Open edX ones.
`learners`	No	Learners with display names, 1 to 100. Use this OR emails; if both are sent, learners is used.
`sendInvite`	No	Have Cubite email each learner a one-click sign-in invite (or the plain enrolment email when no link can be issued). Default false; each result carries emailSent.
`issueMagicLink`	No	Return a single-use 24-hour sign-in link per learner as magicLinkUrl (default true; null for admins, password accounts and people on other Cubite sites). Each one cancels that learner's earlier link. Ignored when sendInvite is true.
`skipPrerequisiteCheck`	No	Enroll even if the course has unmet prerequisites (default false); otherwise those learners fail with missingPrerequisites.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries the real behavioral burden and does so well: partial-success semantics, per-learner failure isolation, server-error behavior with no per-learner results, idempotent re-runs, invite re-sending and sign-in link replacement. It does not explicitly restate the safety profile (non-destructive, no auth prerequisites), but the failure/re-run semantics are unusually thorough. No contradiction with readOnlyHint=false.

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 with purpose and sibling routing before the behavioral caveats, and every sentence carries substantive information rather than filler. It is dense, with long multi-clause parentheticals, which costs a point on readability but not on waste.

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?

No output schema exists, yet the description fully describes the return shape ('Enrolled N, failed M' plus per-learner email, ok, created, emailSent, magicLinkUrl, enrollment / error, missingPrerequisites) and the all-fail error case. Combined with the mutation caveats, an agent has everything needed to call and interpret it correctly.

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 the schema already documents each parameter including defaults. The description adds useful cross-parameter context — sendInvite:true gating email, learners-vs-emails precedence, and the course_list pointer for courseId — plus the redirectTo/externalReference note that lives only in the description, so it exceeds the baseline 3.

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 with explicit scope ('Enroll up to 100 learners in one course in a single call') and directly differentiates from the sibling enrollment_create ('use enrollment_create for one learner or to pass redirectTo or externalReference'). An agent can route between the two without opening either schema.

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?

Gives explicit when-to-use and when-not-to-use guidance: this tool for bulk, enrollment_create for a single learner or when redirectTo/externalReference are needed. It also states the shared rule set inherited from enrollment_create, so prerequisites and invite behavior are unambiguous.

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

All Cubite LMS: Learning Management System 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.

Resources

Need Help?