LearningSuite MCP Server

learningsuite_remove_member_from_courses

Remove a member from one or more courses in LearningSuite by providing the member ID and an array of course IDs. This action updates course memberships directly.

Instructions

Remove a member from 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_remove_member_from_courses"
  }
}

Input Schema

Name	Required	Description	Default
`memberId`	Yes	Member ID
`courseIds`	Yes	Array of course IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It simply states 'Remove a member from one or more courses' but does not mention side effects, reversibility, permissions required, or behavior if the member is not enrolled. This is a mutation tool with no safety context.

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 concise sentence that clearly communicates the action and scope. No unnecessary words or repetition.

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 simple tool with two clear parameters and no output schema, the description is adequately complete. However, the lack of annotations means it does not fully address potential side effects or failure modes, so it is not a perfect score.

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 coverage is 100%, with both memberId and courseIds described directly in the schema. The description adds minimal extra meaning beyond confirming 'one or more courses' matches the array parameter. Since the schema already documents parameters, the description does not need to compensate.

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 uses a specific verb 'Remove' with a clear resource 'member from one or more courses'. It distinguishes itself from sibling tools like add_member_to_courses and remove_member_from_bundles by specifying the target (courses) and the action (remove).

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

Usage Guidelines3/5

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

The usage is implied by the tool name and description, but there is no explicit guidance on when to use this tool versus alternatives such as learningsuite_remove_member_from_bundles or learningsuite_remove_courses_from_group. No exclusions or context are provided.

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

Deploy Server