fix: ask the user to generate instead of generate by default

Author: paoloricciuti

src/lib/mcp/handlers/prompts/svelte-task.ts

@@ -35,7 +35,7 @@ This is the task you will work on:
 ${task}
 </task>
 
-If you are not writing the code into a file, once you have the final version of the code call the \`playground-link\` tool to generate a playground link to share with the user and present the link right after the code. The playground link MUST be generated only once you have the final version of the code and you are ready to share it, it MUST include an entry point file called \`App.svelte\` where the main component should live. If you have multiple files to include in the playground link you can include them all at the root.
+If you are not writing the code into a file, once you have the final version of the code ask the user if it wants to generate a playground link to quickly check the code in it and if it answer yes call the \`playground-link\` tool and return the url to the user nicely formatted. The playground link MUST be generated only once you have the final version of the code and you are ready to share it, it MUST include an entry point file called \`App.svelte\` where the main component should live. If you have multiple files to include in the playground link you can include them all at the root.
 `,
 						},
 					},

src/lib/mcp/handlers/tools/playground-link.ts

@@ -32,14 +32,14 @@ export function playground_link(server: SvelteMcp) {
 		{
 			name: 'playground-link',
 			description:
-				'Generates a Playground link given a Svelte code snippet. Call this tool once you have the final version of the code you want to send to the user to allow it to quickly check the code in the playground. NEVER use this tool if you have already created a file for the component. The playground accept multiple files so if are importing from other files just include them all at the root level.',
+				'Generates a Playground link given a Svelte code snippet. Once you have the final version of the code you want to send to the user, ALWAYS ask the user if it wants a playground link to allow it to quickly check the code in the playground before calling this tool. NEVER use this tool if you have written the component to a file in the user project. The playground accept multiple files so if are importing from other files just include them all at the root level.',
 			schema: v.object({
 				name: v.pipe(
 					v.string(),
 					v.description('The name of the Playground, it should reflect the user task'),
 				),
 				tailwind: v.pipe(
-					v.string(),
+					v.boolean(),
 					v.description(
 						"If the code requires Tailwind CSS to work...only send true if it it's using tailwind classes in the code",
 					),