LearningSuite MCP Server

learningsuite_add_member_to_courses

Add a member to one or more courses by member ID and course IDs. Optionally specify access time, include a login link in course emails, or suppress notification emails.

Instructions

Add a member to one or more courses

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": {
      "memberId": "<memberId>",
      "courseIds": "<courseIds>"
    },
    "name": "learningsuite_add_member_to_courses"
  }
}

Input Schema

Name	Required	Description
`memberId`	Yes	Member ID
`courseIds`	Yes	Array of course IDs
`accessGivenAt`	No	When access was given (ISO format)
`sendLoginLinkInCourseEmail`	No	Include login link in course email
`disableAccessNotificationEmail`	No	Do not send access notification email

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.8/5.0

Behavior1/5

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

The description discloses no behavioral traits beyond the raw action. It doesn't mention side effects like sending emails, permission requirements, idempotency, or what happens on duplicate enrollment. With no annotations available, the description carries full responsibility, but it is too minimal to inform safe usage.

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?

The description is a single, clear sentence that immediately conveys the purpose. It is front-loaded and contains no unnecessary words or repetition.

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

Completeness2/5

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

For a mutating tool with 5 parameters and no output schema, the description is too sparse. It doesn't explain what 'add' implies in terms of notifications, access timing, or potential errors. The schema covers parameter syntax but not the operational context needed to confidently invoke the tool.

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 parameter details are already present in the schema. The description adds no extra meaning beyond phrases like 'one or more courses,' which merely echoes the array nature of courseIds. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 clearly states the action: 'Add a member to one or more courses.' It specifies a verb (add), resource (member), target (courses), and scope (one or more). This distinguishes it from sibling tools like remove_member_from_courses or add_member_to_bundles.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or scenarios where a different tool (e.g., get_member_courses or update_member) would be more appropriate. The description only restates the basic action.

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

Deploy Server